David Newton wrote:I couldn't tell from the TOC if the book covers functional (client-oriented, browser- or UI-based) testing, or if it covers load-testing.
If it covers load-testing does it discuss when it should be introduced, and how?
Chapter 11 covers tests in the fourth "agile testing quadrant" - critiquing the product using technology-facing tests. This includes a variety of non-functional tests. We have a section on performance, load, stress and scalability testing. The order of the four quadrants does not denote the order in which tests should be done. If performance is critical for your application, you might do some scalability testing early on in a release cycle. We recommend setting goals for performance, then deciding on tests and tools. Ken De Souza contributed a short sidebar recommending that you design your performance tests from the start.
This definitely isn't a "how to" book for load testing, but it does provide some guidelines to fitting these different types of testing into agile iterations.
Co-author, with Janet Gregory: Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009) http://lisacrispin.com