The world of tech is rapidly evolving, and developers are against the clock when it comes to creating innovative and flawless products that can keep up with the competition. For DevOps teams to work with the speed and accuracy necessary to make this happen, they have...
How do I create a risk-based testing plan that focuses more coverage on higher priority areas?
Introducing and explaining the “Mixed-Strength Testing” feature.
DesignWise allows you to adjust testing coverage to focus more thorough coverage on selected, high-priority areas
A more powerful risk-based testing strategy (at the parameter level) is generating Multi-Strength test sets, as described in the following example. This feature can be helpful to use in many (if not most) of the plans you will create.
Let’s set the context and the problem we’re trying to address
What we want to do now is to generate a set of scenarios that will focus extra coverage on the high-priority parameters below, while maintaining pairwise coverage for every Value in our plan. Creating a “Mixed-strength” model will allow us to do exactly that!
Comprehensive coverage for all Values in those 3 columns is achieved with one another AND achieves 2-way coverage of all the possible pairs of Values.
The DesignWise test generation algorithm is able to achieve both of these objectives in only 252 tests.
As shown in the screenshots above, we can see that it takes 252 scenarios to achieve 3-way coverage of all of the possible combinations of the 3 parameters with high priority values and that it takes 87 scenarios to achieve 2-way coverage of all of the Values in the plan. In this example, the DesignWise test generation algorithm identified a way to combine both of these objectives into only 252 Risk-Based Tests.
In short, even after focusing additional thoroughness on our three highest priority sets of values, we generated a solution with only 252 Mixed-strength tests (versus almost 2 times that many in the unweighted 3-way coverage option). We were able to focus the additional coverage where we wanted it without generating lots of additional scenarios that we do not have time to execute.