Rigorously test complex systems within an iteration
Test Modeller quickly captures complex systems as easy-to-maintain flowchart models, automatically generating a rigorous set of test cases, data, and automated tests.
|
Automated Test Case Design
|
Manual Test Case Design
|
|
1. Agile Requirements Modelling:
Existing test cases and user stories are automatically converted to accurate flowchart models, with full dependency mapping across components.
|
1. User Stories Perpetuate Defects
Fragmentary user stories and incomplete requirements are written in ambiguous natural language, without mapping between components.
|
|
2. Optimised Test Cases Rigorously Test with Fewer Tests:
Powerful mathematical coverage algorithms generate the smallest set of test cases needed to exhaustively exercise the logic contained in the system model. Granular coverage techniques can also focus testing on new or critical functionality.
|
2. Over-Testing Leaves the Majority of Systems Exposed:
Testers slowly and manually convert user stories to low-coverage test cases that focus repeatedly on "happy path" scenarios. The majority of a complex system's logic is left exposed to defects that are detected late, at a greater cost to fix.
|
|
3. End-to-End Test Automation:
The same model can be used to generate the test data and automated tests needed to execute the optimised test cases, at the same time as they are created.
|
3. Slow and Manual Test Execution:
Test data must be manually found or made for each test case, while the tests are slowly converted into automated test scripts, or are executed manually. This is slow and resource-intensive.
|
|
4. Teams and Information is Kept Aligned Across Delivery Pipelines:
The VIP workflow engine populates existing ALM and project management tools with the optimised test artifacts, using high-performance Robotic Process Automation to keep information aligned across DevOps pipelines.
|
4. Miscommunication and Poor Alignment of Tools and Teams:
Test teams repetitively input the same test steps and test metadata into fields across the numerous tools in use at their organisation. Miscommunications arise and more time is spent on process than development.
|
| 5. Test Automation Reacts to Fast-Changing Requirements:
Change requests and new user stories are imported to the central model, automatically updating the test cases, data, and automated tests associated with every affected component.
|
5. Manual Test Case Maintenance Takes Longer than an Iteration:
There is no way to reliably or automatically identify the impact of a change request across complex systems. Testers check and update the masses of test cases by hand.
|
