Page History
...
Test Case Designer allows you to adjust testing coverage to focus more thorough coverage on selected, high-priority areas
One straightforward risk-based testing technique (at the value level) is to simply enter a specific value multiple times in the “Inputs” “Parameters” screen. Entering “Male, Male, Female, Male” as Values, for example, would result in “Male” appearing three times as often as “Female.”
A more powerful risk-based testing strategy (at the parameter level) is generating Mixed-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 models you will create.
...
Why does such risk-based testing makes sense conceptually?
There are only two possible reasons that a set of 2-way tests could fail to trigger a software defect:
There was a missing test "idea" (e.g., the only way the defect could be found is if the application were tested using a specific operating system and that specific system was not included as one of the parameters/values).
All of the test ideas and test conditions were included as values, but the defect could only be triggered by the scenario that included three or more of those existing test conditions together at the same time.
In our experience working with hundreds of software teams, the first reason (not thinking to include a particular test idea) is responsible for more defects slipping by testing than the second one (specific combinations of 3 or more already-included ideas).
Accordingly, this is what is recommended for testers who are planning to manually execute sets of 3-way scenarios:
Don't*
At least not until you first experiment a bit with executing well-thought-through sets of Mixed-Strength scenarios
Why? 90% of the extra thoroughness you might be looking for can probably be achieved by a well-thought-out set of mixed-strength tests. These tests might be half as numerous as the full, "regular" higher-strength test set.
With the extra time that the team saves by not executing all of those additional tests, they should use it to add more wrinkles/ideas into their testing.
*This advice is for manual testing projects (where the costs of executing extra tests is relatively high), not for automated test execution projects (where the costs of executing extra tests is relatively low).
Examples of good sources for additional testing ideas include these:
J. Michael Hunter's "You Are Not Done Yet" (Link to PDF)
Elisabeth Hendrickson's Test Heuristics Cheat Sheet - Data Type Attacks & Web Tests (Link to PDF)
Bug reports
Your business rules and technical specs
Adding more scope (e.g., adding in an additional type of user, even when different types haven't previously been considered in scope)
Let’s set up the use case we’re trying to address
We have a mission-critical application that includes several large changes in this release. We’ve filled in parameters for our System Under Test, and we see that a 2-way solution based on our variation ideas would require 87 scenarios.
...
Curious to see how many tests would be needed for a more thorough test planmodel? Generate a set of 3-way tests! Unfortunately, this more-thorough solution requires almost 5 times as many tests. Ugh! We don’t have time all of those!
Determine what Values Parameters we want to devote more thorough testing to
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 planmodel. Creating a “Mixed-strength” model will allow us to do exactly that!
...
Another way to look at the set of Risk-Based Scenarios that we have just created is to imagine temporarily removing everything from our plan except model except for the high-priority Parameters. With 3 values for "User Type", 6 for "Customer Authorization Limit", and 14 for "Transaction Exchange (Country)", simple math tells us that to test every possible combination we require 3×6×14 = 252 tests. All 252 of these 3-way combinations are included in the Mixed-Strength (“Risk-Based Testing”) scenarios that we created…
In addition to achieving comprehensive 3-way coverage of the high priority parameters we identified, the 252 Mixed-strength scenarios we created ALSO made sure that we tested every single pair of Values together in at least one test case.
The DesignWise test generation TCD generation algorithm is able to achieve both of these objectives in only 252 tests. 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.
Use "Mixed-Strength" scenarios more often than "regular" higher-strength ones
...
Written by Scott Johnson
Updated over a week ago
...
.
...
Many testers new to this kind of testing are too quick to use sets of 3-way tests when they are seeking more-thorough coverage than pairwise sets can provide
Instead of executing an entire set of higher strength tests, it is usually more efficient and effective to execute a set of Mixed-Strength tests instead. These tests have the ability to include more thoroughness in selected areas (where you want the extra thoroughness). Sets of Mixed-strength scenarios will usually be fewer in number than "regular" higher strength models.
There are only two possible reasons that a set of 2-way tests could fail to trigger a software defect:
There was a missing test "idea" (e.g., the only way the defect could be found is if the application were tested using a specific operating system and that specific system was not included as one of the parameters/values).
All of the test ideas and test conditions were included as values, but the defect could only be triggered by the scenario that included three or more of those existing test conditions together at the same time.
In our experience working with hundreds of software teams, the first reason (not thinking to include a particular test idea) is responsible for more defects slipping by testing than the second one (specific combinations of 3 or more already-included ideas).
Accordingly, this is what is recommended for testers who are planning to manually execute sets of 3-way scenarios:
Don't*
At least not until you first experiment a bit with executing well-thought-through sets of Mixed-Strength scenarios
Why? 90% of the extra thoroughness you might be looking for can probably be achieved by a well-thought-out set of mixed-strength tests. These tests might be half as numerous as the full, "regular" higher-strength test set.
With the extra time that the team saves by not executing all of those additional tests, they should use it to add more wrinkles/testing ideas into their testing.
*This advice is for manual testing projects (where the costs of executing extra tests is relatively high), not for automated test execution projects (where the costs of executing extra tests is relatively low).
Examples of good sources for additional testing ideas include these:
...
J. Michael Hunter's "You Are Not Done Yet" (Link to PDF)
...
Elisabeth Hendrickson's Test Heuristics Cheat Sheet - Data Type Attacks & Web Tests (Link to PDF)
...
Bug reports from this product (or similar products)
...
Your business rules and technical specs
...