Risk-based testing means organizing test strategy around suspected product risks. This means testers perform risk analysis before, during, and after tests are performed: before tests to guide the test process, during tests to adjust the strategy, and after the product is released to learn about risks that were missed in the original planning. Risk-based testing is a powerful way to focus testing and to justify the time and energy it takes to test deeply.
This seminar focuses on risk-analysis as it relates to testing and fits within the Rapid Software Testing methodology. So, we use risk heuristics and focus on assessment rather than measurement of risks, since software risks cannot be measured except in rare situations. Risk assessments are socially constructed, but we show how that process can and should be done systematically and be grounded in evidence.
This is a one-day seminar that is taught online as three 90-minute webinars, plus a gap to do a practical exercise, for a total of 7.5 hours (including breaks).
- The primary goal of this seminar is show you how to confidently perform systematic product risk analysis.
- A secondary goal is to extend your understanding of Rapid Software Testing methodology.
- You are responsible for test strategy in your project.
- You lead people who are responsible for test strategy in your project.
- You want to learn how to be responsible for test strategy in your project.
- You are struggling to explain and defend the focus of your software testing.
- You want to practice risk analysis on a software product.
- You struggle to persuade the team to fix important problems in a timely way.
- You are concerned that your testing may not be oriented on finding the bugs that really matter.
- The headlights analogy as a framework for understanding risk-based testing.
- How mental models control risk analysis.
- How beliefs about risk are socially constructed.
- Heuristics of product risk analysis.
- The cyclic and incremental process of risk analysis.
- How to tell a compelling risk story.
- Why we assess risk but cannot measure risk.
- How to evaluate if testing is good enough.
- How to evaluate if the product is good enough.
How RSTF Compares To RSTE
- Rapid Software Testing Explored (RSTE) presents the methodology of Rapid Software Testing with brief practical exercises and Socratic discussion. This is a foundational class that is good to take before RSTF. Although RSTE does cover the risk conceptually, there is no focused exercise on risk analysis.
How Do I Take This Class?
You can check the schedule to see if there is an upcoming public class.
Or you can email me at james@satisfice.com to inquire. See also my page about how to engage our services.