Accurately capture evolving user requirements
Model complex systems as complete flowcharts in-sprint, using a comprehensive range of importers, scanners, and a UI recorder.
Clear designs, accurate development, and rigorous testing that keeps up with business needs:
Not got time to model? Think again.
With Test Modeller, modelling is:
- Rapid, using a range of importers, an object scanner, and UI Recorder to completely capture complex systems in-sprint.
- Reliable, catching potentially costly design defects before they can reach development and be perpetuated in code.
- Easy-to-use, with simple BPMN-style modelling and a drag-and-drop approach to quickly assemble models from re-usable components.
- Collaborative, using shared requirements models to drive testing and development, keeping business and IT stakeholders aligned.
- “Active”, with flowchart models capable of directly generating test cases, data, and automated tests.
- Reactive, using visual models to incorporate new user stories rapidly, quickly spotting their impact on existing systems and generating rigorous tests to validate any changes made.
Better Design. Better Code. Better Tests.
Test Modeller quickly captures new or existing functionality as easy-to-maintain flowchart models, from which a comprehensive set of tests can be generated and executed automatically.
| Agile Requirements Modelling with Test Modeller: | Hand-written user stories and diagrams: |
|---|---|
Clear and complete visual models are automatically created from existing user stories, scanned objects, and recorded activity. | Incomplete stories pile up over time and are written in ambiguous natural language. There is no dependency mapping between components. |
Design defects are spotted and removed from the visual flowcharts, providing development with a complete and unambiguous mode. | Developers cannot identify the impact of new user stories across complex systems, and defects arise as they misinterpret written user stories. |
Automated tests that exercise all the logic contained in the modelled user stories are generated automatically from the flowcharts. | Testers convert incomplete user stories into tests manually, but this is time-consuming and leaves most of the system exposed to defects. |
New user stories are imported quickly, with the impact of the change reflected across interdependent components. A rigorous test set is generated to validated any changes made. | The impact of a change request across complex systems must be identified manually, with tests slowly updated by hand. Defects arise due to the unforeseen impact of changes made. |
Contact us.
Send us an email
Curiosity Software Ireland
Unit 6, The Mill
Bray
Co. Wicklow
Ireland
Call us now
+353 860 328059 (Ireland)
+1 914 297 7512 (USA)