Your SlideShare is downloading. ×

Continuous Performance Testing

1,303
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,303
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Continuous Performance Testing Mairbek Khadikov
  • 2. Story #1Performance, we are losing it
  • 3. Story #1 New version goes live soon Lets check performanceDeliveryManager
  • 4. Story #1 Performance degraded =Performance Tester
  • 5. Story #1 Lets profile our appDeveloper
  • 6. Story #1 Performance increased on 10%Performance But its still worse than Tester the previous release
  • 7. Story #1 We cant wait much longerDeliveryManager CPU utilization is 50%
  • 8. Story #1 Alert is rased too late
  • 9. Story #2Its all tested, but...
  • 10. Story #2 We deployed new release It passed all smoke tests Works incorrect with loadOperations balancer
  • 11. Story #2 We tested all this featuresQA
  • 12. Story #2 System has acceptable throughputPerformance Tester
  • 13. Story #2 Doh, one singleton unit is not thread safeDeveloper
  • 14. Story #2 Performance test does not check that system works correctly
  • 15. Story #3Forgotten branches
  • 16. Story #3 Performance degraded in the last release candidatePerformance Tester
  • 17. Story #3 What branch exactly impacted performance?Developer
  • 18. Story #3 Ive never heard about the half of this branchesPerformance Tester
  • 19. Story #3 Large projects need a comprehensive performance testing process
  • 20. Story #4Did you test that?
  • 21. Story #4 Production system failed this morning VP ofEngineering
  • 22. Story #4 Two nodes were restarted simultaneouslyDeveloper
  • 23. Story #4 Those nodes consumed to much memoryOperations
  • 24. Story #4 This is a complex scenario we cant do it continuouslyQA Lead
  • 25. Story #4 Simulation of maintenance operations and failures was not a part of testing
  • 26. Performance Testing Revised
  • 27. Performance Testing ContinuousAutomatically test builds
  • 28. Performance Testing Continuous Rise alert flag in case ofperformance degradation
  • 29. Performance Testing TraceableStore all testing results
  • 30. Performance Testing ValidatedGuaranty that system works correctly under workload
  • 31. Performance Testing TransparentResult should include monitoring and profiling information
  • 32. Performance Testing TransparentModules should be tested in isolation where possible
  • 33. Performance Testing PessimisticSimulate potential maintenance operations and failure
  • 34. Thank you @mairbekmkhadikov@gmail.com mairbek.github.com