Summary

Performance testing requires planning. Responsible performance targets, accurate test scenarios, and a reasonable testing strategy all lead to accurate test results. In this chapter, we covered some of the highlights of performance test planning. Everyone uses terms like hit, user , and day , but regrettably we often use them to describe a variety of different concepts. It's important to get agreement ahead of time on the definition of these terms as they are used in your planning.

We also provided some examples of developing performance estimates for your web site. Starting with interpreting data from your existing web site or working with estimates provided by your marketing team, we showed how to create rough estimates for your planning and testing. We also discussed the difference between peak and average load, and emphasized the importance of planning for peak load usage. Appendix A contains worksheets for most of these estimates to help you better organize your data and develop a test plan We suggest you use this plan to drive discussion with the various parties involved with the web site (marketing, management, development, etc) in order to achieve consensus on your performance goals before beginning the test.

Also, we discussed the basics of scenario development and scalability testing. Up-coming chapters explore these topics in greater detail, complete with a case study applying best practices. However, as you learn more in these chapters about executing a performance test, keep in mind the importance of a good test plan. If your fundamental goals and assumptions prove erroneous, your test results are worthless.