Risk-based Testing: When You Can't Test It All

Testers everywhere have experienced this scenario-the development cycle slips and now testing gets two weeks instead of four to complete its work. How do you systematically determine what to test and what not to test in this time-constrained situation? How do you determine the right amount of testing so that you are not doing too much or too little? Reán Young shows how using a risk-based approach helps to identify test strategy options based on a combination of business and technical factors. They evaluate risks in each area of the application and devise a test plan that ensures that the most critical components will be tested before the deadline. This approach encourages the entire project team to take ownership of determining what should be tested. By implementing risk-based testing in your organization, your test team will have the tools to target, prioritize, and maximize the value of testing-especially when time is short and the pressure is on.