Page History
...
Starting with the most obvious approach, you can (1) model constraints as well as you are able to do so with the constraint handling capabilities available today, (2), generate your optimized scenarios (which would erroneously include a few 3-way / n-way combinations you would like to prevent), then (3) you would manually fix the wrong combinations after they appear.
You could use DesignWise’s TCD’s Freeze Feature to turn your generated set of scenarios into forced combinations of inputs. With your tests in the “frozen” state, you could then manually correct any prohibited combinations by manually over-writing any “impossible to test for scenarios” that were generated. If you expect to be modifying this set of tests multiple times, this option is recommended (because the “fixes” you make on the Frozen Tests (Forced Interactions) screen will remain in place for all future test sets you generate from this model.
...
To understand this approach, keep in mind that DesignWise treats Test Case Designer treats information as text without over-analyzing the underlying intention.
...
Side note: for automation (where the literal value is more important), the value expansion can be added to “Yes*” to replace the value name on export since DesignWise TCD Automate only reads value expansions, if they exist.
...
Lastly, on the Forced Interactions screen, we force the combination of Q2=Yes with Q1=No and accept the warning that informs us that our constraints logic would make it impossible for marks that combination to ever appear. as invalid/impossible.
Doing so will result in the Forced Interaction overwriting the plan’s model’s constraints logic.The net result of this is that we We would get one scenario (and only one) in our plan data table that would include both Q1 = No and Q2 = Yes. And the Correct correct Question 3 value would appear (“Not displayed”) because we forced that specific value for Question 3 to appear in the Forced Interactions screen. The other values that appear for Question 3 are properly limited from the rules on the Constraints screenit.
We still get the coverage of all pairs and eliminate invalid combinations.
...