The document discusses best practices for agile performance testing. It recommends defining key performance indicators, automating tests to run continuously, and monitoring tests and systems to quickly resolve and prevent performance issues. Frequent smaller tests are better than infrequent large tests to catch issues early in development iterations.

1. The Secret Art of Agile Performance Testing Alois Reitbauer, dynaTrace Software

2. The Classical Approach

3. Waterfallsarepretty

4. But mightgetscary

5. Dream Iteration ComfortZone Test Iteration Reality Iteration Test

6. Dream Iteration Iteration ComfortZone Test Iteration Iteration Reality Iteration Test Iteration

7. NFRs and Maslow

8. The Focus Problem

9. Methodology

10. The Agile Approach

11. DefiningourStrategy Start Early Break in Pieces Test Continuously

12. Creating Focus Automate Risk Regular Testing Skip Impact

13. Frequency vs. Granularity JUnit-based Tests (2x day) Total System Tests Long-running Stabiltiy Tests (2 w duration) Granularity Frequency

14. Granularity Comparability Complexity Quality

15. Define KPIs Throughput Response Time Memory Consumption Other KPIs …

16. Follow a Strategy Monitor GainVisibility Resolve Reduce ResolutionTime Prevent ProactivelyAvoidProblems

18. Whichinformation do youwant?

19. Whatdescribesyoursystem?

21. Lessonslearned

22. Profilingis not enough Goodforfindingproblems Resultcomparisonhard Only valid untilnextcheck-in Toomuchwork

23. The Life of a Log Statement Enter the code publicvoidfoo (){ … // do something bar (); } publicvoid bar (){ … // do somethingelse Logger.log (“executiontook“ + time); }

24. The Life of a Log Statement Somebody changes something publicvoidfoo (){ … // do something if (condition) bar (); else otherBar (); } publicvoid bar (){ … // do somethingelse Logger.log (“executiontook“ + time); }

25. The Life of a Log Statement Your code gets deprecated publicvoidfoo (){ … // do something newBar (); } publicvoid bar (){ … // do somethingelse Logger.log (“executiontook“ + time); }

26. Measurements

27. Stability of Tests

28. UseDedicated Hardware Comparability Stability Efficiency

29. Trends in Unstable Tests

30. Create Instability .. addingsomevolatilityincreasesthelikelyness todiscoverproblems …“

31. Testing scalability Small Dump Operations Big Dump Operations

32. Understandyourmeasurements Response Time and GC Response Time only

33. Motivateyourteam

34. Howtomakedeveloperswritetests #1 Heroism #2 Boomerang #3 The otherguy #4 Bug me not #5 Feedback #6 Code vs. Wine #7 Newb vs. Noob

35. Test Case Complexity First Start dynaTrace infrastructure Whenready Start n WebSphereinstances on servers … Whenready Start LoadtestagainstWebSphereservers After loadteststart Execute testcase

36. Making complex things easy @DtdRemoteSud( host = "lab2", name = "WAS7.0", startupPriority = 1, postStartClosure = WaitForWebSphereSudIsUp.class ) private SudInterfacewebSphereSud;

37. Findingtheresponsiblecode Version Control History Lookup

38. E-Mail Notification … betterhumans

39. WrapUp Say „Yes“ Focus Define KPIs RedefineDone Remove Barriers Automate Monitor Resolve Prevent

40. alois.reitbauer@dynatrace.com Mail blog.dynatrace.com Blog AloisReitbauerTwitter