Visual Behaviour Driven Development

Visualise and maintain your BDD.

Automatically convert Gherkin scenarios to easy-to-maintain models, and generate rigorous automated tests and data directly from them.

Read The free eBook



a truly test driven approach


With Test Modeller, Behaviour Driven Development is:
  • In parallel, with design, development and QA working form the same central models to deliver quality systems earlier, and at less cost to the business.

  • Faster, with automation of the slow and manual tasks that slow QA teams down. Maintain a complete set of tests and data directly from Behaviour Driven requirements.

  • Truly test drive, using automated techniques to generate the most rigorous set of automated tests possible, directly from the system designs.

  • Simple and easy-to-implement, with intuitive visual models and a range of connectors to work directly with existing assets and tools.

Try Test Modeller

Curious About


Sign up to receive Curiosity's latest BDD research, and learn how visual modelling can unlock the value of behaviour-driven development at your organisation.

Get the free BDD research

design, development and qa, all working from the same page


Test Modeller introduces the rigour of Model-Based Testing to Behaviour Driven Development. You can maintain complete designs and tests, while implementing fast-changing requirements in sprint.


Visual BDD with Test Modeller
Behaviour Driven Development

1. Capture Fast-Changing User Needs Accurately:

Gherkin specifications are converted to logically precise models, using a simple copy-and-paste approach.

New Gherkin Specifications are Captured:

BDD provides a flexible approach to capturing new user stories quickly as Behaviour Driven scenarios.

2. Eradicate Defects Before They Enter Your Code:

The flowcharts provide complete and unambiguous specifications for developers to work from. Models consolidate the Gherkin feature files, while any missing logic is easily spotted and added to the visual flowcharts. Developers know exactly what needs to be updated across complex systems.

2. Incomplete Specifications Introduce Costly Bugs:

The discrete specification files are added to a mass of unconnected scenarios. Developers cannot identify what needs updating to implement a new scenario across complex systems. The ambiguous, incomplete nature of scenarios written in natural language introduce further defects.

3. Detect Defects Earlier, at Less Cost to Fix:

Rigorous tests are generated automatically from the requirements models, using mathematical algorithms to create the smallest set of test cases that cover the model. Tests cover the negative scenarios needed to detect bugs earlier, and at less cost to fix.


3. Resource-Intensive Testing Leaves the System Exposed to Bugs:

Tests created from the incomplete Gherkin scenarios are themselves incomplete, and wastefully test the same logic repeatedly. They do not test the negative scenarios most likely to cause severe defects, and the system remains exposed to costly bugs.

4. “Just in time” Data for Every Possible Test:

Test data is defined dynamically using a comprehensive range of easy-to-use functions. It is found or created for very test during execution, for rigorous testing without bottlenecks.

4. “Low-variety Data Undermines Testing Speed and Rigour:

Test data must be found among large copies of production data or is created by hand. This is slow and complex, and risks potentially costly non-compliance with data protection regulations.

5. Accurately Deliver the Very Latest Desired Behaviour:

Automated tests and data are regenerated after the model changes, rigorously testing from the latest Behaviour Driven requirements.

5. Testing and Development Fall Behind User Needs:

Testers manually check and update existing tests and data every time the system changes. QA quickly lags behind fast-changing user needs.


Speak with an expert

Introduce the rigour of Model Based Testing to Behaviour Driven Environments:

Book a Demo