Scenario | objective:

Test Data Automation (TDA) along with Test Modeller is a tool to model out business logic. Once requirements are modelled these contraints drive user journeys. What would you model out using the contratints and tags feature demonstrated here? In this example about a golfing tournament to see which golfers are allowed to play. Hard outcome: See how TDA features like: coverage, constraints and tags are managed for automating test case scenarios.

UI at a glance

Pulling focus on Test Modeller’s UI for using constraints, tags and coverage to model out business logic.

Ribbon menu: Test Data Variables | Assignment & Configure Tags | Rules

Task block with rules and tags

Task block (no rules or tags)


Task block with rules


Canvas nodes: Task blocks | Waypoints

Panes: Test Data Variable Assignments | Scenarios

🔗 Test Modeller UI

A word from one of our Solutions Architects

What’s the relationship of constraints (for modelling business logic)?

Within Test Modeller there are multiple entry points/ways of defining constraints which makes Test Modeller an agile TDA tool. This flexibility allows business logic to be embedded into models with ease, generating paths that reflect these contraints in the scenarios panel.