Scenarios & Critical Paths

Real users do not run one test case in isolation. They move through a journey, carrying data from one step to the next. Scenarios let you model those journeys end to end, and Critical Paths let you flag the ones the business cannot afford to break.

Who it’s for#

QA engineers and product owners who need to validate complete workflows, not just isolated features.

What it does#

• End-to-end journeys — combine multiple test cases in sequence into a single scenario.
• Data flow — pass data from one step to the next so each stage uses real upstream output.
• Critical path tagging — identify and prioritize the business-critical workflows that matter most.
• Approval gates — put sign-off on critical paths so important journeys get extra scrutiny.

How it works#

A scenario chains test cases in order and carries data forward between them, so a later step works with what an earlier one produced. Marking a scenario as a critical path raises its priority and can require approval before it is considered complete.

Why it matters#

Testing whole journeys catches the failures that only appear when features interact. Flagging the critical paths means your highest-risk workflows get the attention they deserve before a release goes out.