This presentaion provides steps that are necessary for implementing of performace test solution for nightly build validation for regression. It doesn't have detailed instructions. If detailed steps are needed contact the author.

2. CI Agile Performance Testing in Action
Step-by-Step
Serghei Radov

3. serghei.radov@gmail.com
https://github.com/grinslife
Presentation will be available on
https://speakerdeck.com/grinslife
http://linkd.in/1pFEOz9

5. Drawbacks :
• manual or scheduled running
• manual results analyzing
• manual reporting
• monthly build investigation
• lack of commits tracking
Lessons learned :
- scheduled running is not automation yet
- reporting eats our time even with templates.
- last build testing make debugging and changes difficult

6. What is next?
Find puzzles and solve it!
Jenkins on HP
Host
Performance
Center
Environment
Notifications
HP Analytics
Reporting

7. Environment
Environment deployment
- Check for developers’ deployment builds, they have them but don’t speak about them
- Developers deploy for their needs . Customize it for yourself. Code, Scripts, Reboot
- Add Environment monitors (e.g. Site Scope, Zabbix)
- Roll up your databases (developers use empty DBs) , plug to App server (HP ALM)
- Run smoke before full performance test

8. So
WHAT?

9. Performance
Center
- Get your tests organized and stored at stable place. (E.g. Performance Center).
- Run them more than two times and check that they are stable even after a few runs.
- Collate results and investigate ability to automate.

10. Setup Job in Jenkins to trigger Performance Run
- Jenkins calls PC Scenario and asks PC to run it based on scenario ID
- Tracks execution status

11. Building remotely on ALM-DEV-VM in workspace
Validating parameters before run
Trying to login
[PCServer='PC Server Name', User='PCoEJenkins']
Login succeeded
Sending run request [Domain='DEFAULT', Project='NightlyAutomation',
TestID='218', TestInstanceID='19', TimeslotDuration='7:30(h:mm)',
PostRunAction='Collate And Analyze']
Run started (TestID: 218, RunID: 250, TimeslotID: 20534)
RunID: 250 - State = Initializing
RunID: 250 - State = Running
RunID: 250 - State = Stopping
View report: http://PC ServerName/jenkins/job/…/Report.html
Logout succeeded
Result Status (PC RunID: 250): SUCCESS
Build step 'Execute HP tests using HP Performance Center' changed build result
to SUCCESS

12. ALM.RunTestSet
<target name="ALM.RunTestSet">
<echo> Jenkins is downloading PC results </echo>
<exec executable="${RunTestSet}RunTestSet.exe"
failonerror="true"/>
</target>
ALM.CheckStatus
<target name="ALM.CheckStatus">
<echo> Jenkins is downloading PC results </echo>
<exec executable="${CheckStatus}CheckRunStatus.exe" failonerror="true">
<arg
value="${env.ALM_ver}.${env.consolidated_number}.${env.platform_number}"/>
</exec>
</target>
<target name="main"
depends="about.me,prep.properties.file,refresh.license,unins
tall.qc,clean.DB,install.qc,start.qc,verify.server,save.logs"/>

14. Reporting

15. Challenges
- At the beginning it fails every time you run it
- I have unanswered questions… Whom I can address them?

16. Resources
http://oliveremberton.com/2014/how-to-find-your-passion/
https://speakerdeck.com/bmuschko/building-a-continuous-delivery-
pipeline-with-gradle-and-jenkins
https://speakerdeck.com/bmuschko/web-application-deployments-
with-gradle-from-the-developers-machine-to-continuous-
deployment