This chapter discusses what is perhaps the weakest link in the application life cycle—automated testing, or load testing,1 as part of the QA process. From my firefighting experience, I have found that the more I know about a stakeholder’s QA practices, the easier time I will have getting visibility into their operational issues. Understanding their gaps in application testing often leads me directly to what is troubling them in production. Visibility is what I use to both confirm their suspicions and reveal issues they had not considered.
Unable to display preview. Download preview PDF.
- 1.Wikipedia, “load test,” http://en.wikipedia.org/wiki/Load_test
- 2.Wikipedia, “software performance testing,” http://en.wikipedia.org/wiki/Software_performance_testing
- 3.Wikipedia, “acceptance testing,” http://en.wikipedia.org/wiki/Acceptance_testing
- 4.Wikipedia, “regression testing,” http://en.wikipedia.org/wiki/Regression_test
- 5.Wikipedia, “certification,” http://en.wikipedia.org/wiki/Certification
- 6.Wikipedia, “user acceptance testing,” http://en.wikipedia.org/wiki/User_acceptance_testing#User_acceptance_testing
- 7.Wikipedia, “software performance testing,” http://en.wikipedia.org/wiki/Software_performance_testing
- 8.Wikipedia, “test plan,” http://en.wikipedia.org/wiki/Test_plan
- 9.Wikipedia, “Scenario (computing),” http://en.wikipedia.org/wiki/Scenario_(computing)