Page History
...
In the financial implementations, each system is usually contributing a “fair share” of parameters to the TCD model, and the key characteristic is the model shape – more “horizontal”, with fewer factors but larger value lists (Claims Processing in Insurance is another area with similar model shapes, unlike the typically “long and narrow” policy side).
System-to-system modeling is not likely to hit the 256 parameter limit in TCD, so you have the flexibility of including factors that are less important, but are necessary for “passive regression” traceability and/or automation (and could increase your defect prevention).
...
Once the draft model is created, the auto-generated Mind Map presents an intuitive view of the model elements and can be easily shared for collaboration and approval.
This approach allows teams to communicate clearly and collaborate efficiently by confirming early in the testing process that 1) all critical aspects have been accounted for, and 2) they have been included at the right level of detail (which is one part of the TCD answer to “how much testing is enough?”).
...
The horizontal model shape we mentioned earlier increases the benefits delivered by a relatively new TCD feature – multi-value constraints.
They allow specifying the rules in a faster and more concise manner compared to the standard icon view (if you do not see the toggle in the top left of the Constraints screen, feel free to reach out to us and request beta access).
...
The resulting scenarios table could look like this:
The ability to iterate at this step and quickly regenerate test cases (based on, e.g., requirement updates) for review provides immense help clarifying ambiguities much earlier in the process.
...
If we now analyze the interaction coverage achieved and compare it with the typical manual solution, the results would often look like this:
As you can see, TCD-generated tests benefit from Intelligent Augmentation that ensures coverage of both (1) all specified requirements and (2) every critical system interaction. Our scenarios consistently find more defects than hand-selected test sets because interactions are a major source of system issues.
...
Note: “!” sign means negation of the values in the filter. You can check the “Usage” button on the Automate screen or the “Getting Started with Automate” guide for more details about the syntax rules.
...
The goal of applying TCD is to deal with such challenges of manual test creation as prolonged and error-prone scenario selection, gaps in test data coverage, tedious documentation, and excessive maintenance.
