Page History
...
The default 2-way set of scenarios generated by DesignWise Test Case Designer is often a solid choice when it comes to the balance of quantity and quality. However, it may not be right for you depending on the project scope, timelines, etc.
...
This method leverages the Analysis features of DesignWiseTCD, specifically the Coverage Matrix in this example:
...
Side note: if you are generally happy with, say, the 80% state but there are a few gaps you want to close, forced interactions Forced Interactions could be used to achieve that efficiently (if moving the slider does not).
...
Please note – when you export or sync test sets, 100% of your tests will be exportedmigrated, so you would need to remove the extra scenarios post-exportafter the export/sync operation.
Strategy 2 – Adjust the coverage dial setting away from 2-way
It is common that parameters in the model do not all have the same level of significance, therefore risk-based testing is applied. In DesignWiseTest Case Designer, that feature is called “mixed-strength testing”.
...
Potential downside – especially early in the project, the exact settings are often “best guesses” based on personal judgments.
Strategy 3 – Change
...
how you describe your inputs (e.g., with
...
optimizations to Parameters, Values, and/or Value Expansions)
It is also common that not all parameter values are equally important – the system rules can be structured in such a way that ages within a certain range behave similarly, state groups have the same laws, and roof shapes have the same coefficients in the pricing engine.
The DesignWise TCD features to account for that are the variations of "Equivalence Classes" approach - Ranged Values and Value Expansions:
Keep in mind the system rules in mind when applying this method as it is not possible to apply constraints to value expansions in TCD.
Side note: it is not required to have all values grouped into expansions or to have ranges cover the whole continuum (i.e. it’s ok to have a break between 50 and 55 as long as the ranged values don’t overlap).
...
Potential downside – excessively aggressive grouping may lead to some value expansions being completely removed from scenarios (i.e if there are 10 expansions, but 8 scenarios with the value, the last 2 expansions would never be used).
Strategy 4 – Add "artificial" constraints
The general logic of this method is invalidating interactions that can happen but we are not interested in them.
...