A 45-minute webinar discussing how agile performance testing helps automate and scale test processes.

1. How Agile Performance
Testing Helps Automate and
Scale Test Processes
Troy Presley

2. Why Do We Test?

3. Only

5. 1+1=2
Accuracy
(No bugs / Matches Spec)
Performance
(Low abandonment / Within SLA’s)
Goals of Testing

8. Goals of
Performance
Testing
Performance Scalability

9. Goals - Performance
Don’t keep them
waiting..
Not all applications have the same
time-sensitivity, but you should
always know what the performance
tolerances or SLA’s are and be able
to measure compliance
Load impacts performance. Do you
know when you should start
worrying?
Sudden changes in performance can
indicate deeper problems. Catching
these changes early creates
opportunities for preemptive

10. Goals - Scalability
Know Your
Limits
How many users/devices/requests
do you expect?
What is the highest utilization you
want/need to support?
Do you know how your applications
will react at 2x normal load? 5x?
10x?

11. +
Load Testing
=
Consistent Performance
Measurements
More Efficient Use
Of Testing Team Effort
Ability to Support
More/Better Test Cases

12. Typical Continuous Integration Cycle
Unit Tests
Unit Tests
Integration Tests
UAT Tests
Performance Tests

13. Typical Continuous Delivery/Deployment Cycle
Unit Tests
Unit Tests
Integration Tests
UAT Tests
Performance Tests
DEPLOY

14. Suggested Performance Tests
On Each BUILD:
Small (10 – 100 virtual users)

15. Suggested Performance Tests
On Each DEPLOY:
Large (80-100% of expected load)

16. Traditional vs Agile Performance Testing
Real World Example

17. Traditional vs Agile Performance Testing
Real World Example
Traditional Performance / Load Testing
Performance Tests per Release 30
Manual Effort per Test 4h
Total Time per Release 120h
Agile Performance / Load Testing
Performance Tests per Release 30
Manual Effort per Test 0h
Total Time per Release 0h
*Script creation and editing is assumed to be the same in both cases

18. ’s Solutions

19. LoadTest Portal

20. Traditional vs Agile Performance Testing

22. AWS CodePipeline
Integration Example

29. Summary
 Testing should target Customer Satisfaction
 This includes Performance and Scalability
 Use Performance / Load Tests to consistently measure these
 Use your CI/CD solutions to automate Performance / Load Tests
 This will reduce or eliminate Manual Effort in testing
 Allowing for More Robust tests that can be run More Frequently
 Use the results to Automatically Gate builds or deployments

30. Thank You
Contact Info:Troy Presley – troy.presley@apicasystem.com
Sales – sales@apicasystem.com
Support – support@apicasystem.com
Additional Info:Apica Synthetic Monitoring – http://www.apicasystem.com/monitoring
Apica Load Test Portal – http://ltp.apicasystem.com/load-testing
Zebra Tester – http://zebratester.com