Explore Curiosity's Platform Use Cases

Our innovative quality solutions help you deliver rigorously tested software earlier, and at less cost!

Test Modeller                    Use Cases

Explore a range of Test Modeller use cases and solutions!

Helpful Resources

Discover a range of helpful resources for getting started with our solutions!

Explore Curiosity's Resources

See how we empower customer success, watch our latest webinars, explore our newest eBooks, read our blogs, and more.

Latest Resources

Explore a wide range of the latest resources from the Curiosity team!

Customer Success Stories

Learn how our customers use our tools to achieve success!

Help & Support

Explore the helpful links below if you need any help.

Creating Quality Since 1995

Curiosity are your partners when designing, building and rigorously testing complex systems in short sprints!

Get To Know Curiosity

Explore our history, learn about our team and the latest Curiosity news!

Customer Success Stories

Learn how our customers use our tools to achieve success!

Connect With Us

Reach out to our team or keep up to date with our latest news!

Test Modeller Logo Agile Requirements Modelling

Accurately capture evolving user requirements.

Model complex systems as complete flowcharts in-sprint, using a comprehensive range of importers, scanners, and a UI recorder.

Try Test Modeller  Schedule a Demo




Don't have 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.

  • 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.

Download Test Modeller Flyer


Eljin 3D

8X Faster Test Creation At Eljin Productions

Learn How Models Drive Rigorous Testing at Eljin

Discover the benefits Eljin Productions achieved when using Test Modeller to successfully launch a business-critical payments platform using model-based test generation and synthetic test data generation.

read our success story


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 With Diagrams:
1. Automated Agile Requirements Modelling:

Clear and complete visual models are automatically created from existing user stories, scanned objects, and recorded activity.

1. Ambiguous User Stories Introduce Defects

Incomplete stories pile up over time and are written in ambiguous natural language. There is no dependency mapping between components.


2. Clear and Complete Designs Drive Test and Development:

Design defects are spotted and removed from the visual flowcharts, providing development with a complete and unambiguous mode.

2. Costly Bugs are Perpetuated Throughout Code:

Developers cannot identify the impact of new user stories across complex systems, and defects arise as they misinterpret written user stories.


3. Testing Detects Bugs First Time Round:

Automated tests that exercise all the logic contained in the modelled user stories are generated automatically from the flowcharts.


3. Slow and Manual Testing Catches Defects Late:

Testers convert incomplete user stories into tests manually, but this is time-consuming and leaves most of the system exposed to defects.

4. Reactive Automation Keeps Up With Change:

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.


4. Testing and Development Falls Behind Changing User Needs:

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.