Page History
...
While functional testing is a common entry point for DesignWise implementations 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 dependencies (and, consequently, in number of important possible interactions).
...
In such situations, teams use DesignWise to TCD to quickly determine the optimal answers to both (1) “how many tests?” and (2) “which specific tests?”.
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 the trade.
...
Test Case Designer Solution & Modeling Process
Building a Model – Step 1 – Parameter & Value Selection
...
In the financial implementations, each system is usually contributing a “fair share” of parameters to the DesignWise planTCD 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 DesignWiseTCD, 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).
...
For convenience, we suggest keeping the parameters in the flow order on the first screen. For the same purpose, elements like this can serve as visual dividers on the Parameters/Scenarios screens and are optional:
Once the draft plan is 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.
...
Note: business logic for parameters like User Profile often involves more than 2 factors, which may complicate the implementation of DesignWise TCD constraints. You can refer to the “How to Implement N-way Constraints in DesignWise” Test Case Designer” article for available methods, and we are working on improving that functionality in the future.
...
The last point at this step is the algorithm thoroughness selection. System-to-system DesignWise models TCD models typically utilize 2-way or Mixed-strength (depending on the parameter structure, project criticality, etc.). The dropdown settings in Mixed-strength are generally chosen based on the following parameter logic:
...
For this example, we will assume that User Profile (System A “outcome”), Account Type (System B “outcome”), and Order Type are critical for the release and deserve 3-way, the rest of the plan model stays at 2-way because we only included the important variables.
...
The effective combination of the level of detail in Parameters and the business-relevant coverage strength in Scenarios guarantees that the DesignWise algorithm Test Case Designer algorithm optimizes your total model scope to have a minimal number of tests that cover all the important interactions.
And next, we will discuss the last piece of the core testing “puzzle” – given the total scope, how we can use DesignWise visualizations Test Case Designer visualizations to select the right stopping point.
...
When integration scenarios are created by hand, they often represent a very fragmented view of the system and struggle with redundancy or omissions. Instead, DesignWise maximizes TCD maximizes the interaction coverage in fewer scenarios and provides complete control and traceability for each of the steps in the test case.
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, DesignWiseTCD-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.
...
We are observing more & more teams switching to BDD, so we will be covering DesignWise Automate TCD Automate in this article, but most general principles also apply to Manual Auto- Scripts.
First, the overall script structure is completely up to you. The number of steps, length of each, number of parameters per each, etc. depend on your guidelines for both test design and execution – DesignWise has Test Case Designer has the flexibility to support a wide range of preferences.
...
Lastly, we strongly recommend sharing the DesignWise models TCD models with automation engineers early in the process to allow them enough time to review and provide feedback on step wording, value names, etc.
...
In conclusion, the combination of DesignWise features Test Case Designer features will allow you not only to quickly generate the optimal set of scenarios but also to answer the “how much testing is enough?” question with clarity & confidence.
The image above should be familiar from our other educational materials, and hopefully, it underscores the notion that the process & methodology are not strongly dependent on the type of testing, type of system, industry, etc.
The goal of applying DesignWise is 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.
...