Countless thousands of people create test cases and perform testing on product in the software industry. Yet few of us, when challenged, can concisely and compellingly explain why we chose to do these tests instead of those tests. This leads to testing that is wasteful, unagile, and disrespected. Good test strategy solves that problem. Test strategy is the set of ideas that guide our choices about what testing to do. Knowing how to construct, explain, and critique a test strategy is the gateway to credibility as a tester. This seminar focuses on strategy as it relates to testing and fits within the Rapid Software Testing methodology. So, we approach strategy as a heuristic, not just a document. We look at it from a social and general systems perspective. Although we won’t focus on risk analysis, we will look at how risk maps to test activities.
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. In 2006, he became co-author (with James Bach) of Rapid Software Testing (RST), a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Since then, he has flown over a million miles to teach RST in 35 countries on six continents. Michael has over 30 years of experience testing, developing, managing, and writing about software. For over 20 years, he has led DevelopSense, a Toronto-based testing and development consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.