Page History
...
While functional testing is a common entry point for Test Case Designer implementations, and we have multiple articles describing the benefits achieved, integration testing (both system-to-system and E2E) is often even more applicable because of the increase in scale and number of several dependencies (and , consequently, in number of several important possible interactions).
However, with that increase comes the greater difficulty in decision making which leads to the major challenge in testing complex systems – “how much testing is enough?”
...
We will describe how these benefits come to life on the generalized example of a wealth management implementation where System A handles risk profile evaluation (like this), System B – opening an account (like this), and System C – placing places the trade.
Test Case Designer Solution & Modeling Process
...
In the financial implementations, each system is usually contributing a “fair share” of parameters to the TCD model, and the . The key characteristic is the model shape – more “horizontal”“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 factors, but are necessary for “passive regression” traceability and/or automation (and could increase your defect prevention).
...
That way, any reviewer could clearly see, e.g., which combinations of qualifying questions you have covered and which you have intentionally omitted (pipe delimiters are not special/required).
For convenience, we We suggest keeping the parameters in the flow order on the first screen for convenience. For the same purpose, elements like this can serve as visual dividers on the Parameters/Scenarios screens and are optional:
...
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?”).
...