2. • Create controllable JMeter tests
• Configure Maven to create a repeatable cycle
• Run this “build” in your CI server every 8 hours
• Find performance regressions faster
3. WHY?
• Catch regressions quickly
• Stop hunting for bugs
• Code with confidence
• Know the performance cost of features
• Fearless external dependency upgrades
• Go home on time
5. ATLASSIAN
• JIRA - Issue management
• Confluence - Enterprise Wiki
• Bamboo - Continuous Integration
• FishEye, Crucible & Clover - Dev Tools
• Crowd - Single Sign-On.
6. BEFORE WE BEGIN
• Continuous Integration is critical
• Keep code working with Unit and Functional
tests
• Broken or irregular builds means no code to
performance test
• Performance testing is NOT a replacement
for other testing (but it helps)
7. PROCESS
• Write code (1-6 months)
• Compile code
• Send it to QA (or Production?!)
• Performance Regression
• PANIC!
No performance testing!
8. A BETTER WAY
• Write code
• CI compiles code and runs tests
• Send it to QA (or Production?!)
• Performance Regression
• PANIC!
No performance testing!
9. A BETTER WAY 2.0
• Performance test artifacts as soon as they
pass Unit and Functional testing
• Fast feedback for developers
• No Surprises
22. MAVEN PROFILES
• Invoked on command line
• eg: mvn verify -Pmysql, tomcat5, dataset1
• Configuration in profile is added to build
• Use for a wider variation in test
environments
• Use profiles for individual “work units”, eg
JMeter
24. REPORTING
CHRONOS
• Available in maven
• eg: mvn site / mvn chronos:report
• Generates graphs and a numerical report
• Can compare to historical data
• Static :(
33. TIPS
• Allocate time for fixing tests
• Your tests WILL break
• Work out a process for fixing bugs
• Gather as many artifacts from each test run
as possible
• React sooner rather than later
34. Q&A
gbarnett @ atlassian . com
@georgebarnett
Code samples online soon!
blogs.atlassian.com/developer
Meet Atlassian @ The Summit:
May 31 - June 2 in SF
www.atlassian.com/summit