Agile Performance tests through CI

Not all automated performance tests are useful for CI ..So far there a few things that very useful to be integrated as part of CI. This was my presentation in Agile Testing Days 2013,Berlin on 31st Oct 2013.

Transcript

1. @fairul82 Fairul Rizal AGILE TESTING Continuous Integration to Continuous Improvement
2. FAST,CHEAP,SCALABLE
3. • Measure application behavior under normal and anticipated peak load conditions. • Goal: Response time, CPU%, Memory%, Throughput, I/O etc. Load Testing • Measure application robustness, availability and reliability under extreme load conditions • Goal: Sync issues, race conditions, memory leaks, weak points etc. Stress Testing
4. No ESCAPE
5. 30% 40% 10% 20% application server architecture database client network *Source: PERFORMANCE inhibitors
6. You want to test BETTER ?
7. BUT…
8. NO TIME
9. SOLUTION Continuous Integration in AGILE performance testing
10. TOOLS Subversion Jenkins,Perf &TAP Plugin Jmeter Yslow! PhantomJS
11. Run tests every time there’s changes to the codes
12. 1: Front End Install PhantomJS http://phantomjs.org/download.html Download Yslow for Phantom JS http://yslow.org/yslow-phantomjs-3.1.8.zip In Jenkins, enable TAP plugin, rules and notification and add the command into building job $ phantomjs -f junit http://test-page-here > yslow.xml
13. Yslow! evaluates website against the best practices at front-end.
14. OUTPUT REPORT IN JENKINS
15. 2: Back–End(simulate virtual users) Install JMeter http://jmeter.apache.org/download_jmeter.cgi In Jenkins, enable perf plugin , perfmon, rules and notification, add the command into building job $ jmeter -n -t <testplan.jmx> -l <log>.jtl
16. OUTPUT REPORT IN JENKINS
17. LESS THAN 10k user loads 10 minutes ??
18. The Cloud!
20. DISCLAIMER “automation can be useful , however a thorough agile performance tests still require a HUMAN BRAIN to perform analysis of result to find meaningful conclusion”
21. Thank you! @fairul82 fairul.fahrurazi@gmail.com