#
Scenarios
Package inputs and credentials into named run variations and fan them out across a suite.
A scenario is a named set of workflow input values paired with credentials. Instead of duplicating a flow to test it as an admin and as a member, or against staging and production, you define one flow and several scenarios — each a reusable run variation.
01Defining a scenario
Open your flow in Flow Designer and, with no step selected, use the Configure tab. A scenario sets:
| Part | What it does |
|---|---|
| Name | How the scenario appears in the run form and results, e.g. Admin – staging |
| Values | Overrides for the flow's workflow inputs |
| Credentials | Which credential each login uses for this variation |
| Default | Marks the scenario used when none is chosen — at most one per flow |
| Include in suite | Whether a suite run fans out a run for this scenario |
Define inputs for the fields that vary across test cases first (see Variables & macros), then build scenarios that supply concrete values for them.
02How scenarios run
- On its own — pick a scenario when you run the flow; its values and credentials apply for that run. With nothing chosen, the default scenario runs.
- In a suite — every scenario marked Include in suite produces its own run, so one flow covers several variations in a single suite run. If no scenario is included, the flow runs once with no overrides.
Each scenario run records which scenario it used, so results stay attributable to the account, environment, or role under test.
03Best practices
- Name scenarios for the variation they represent — the role, environment, or account — so results read clearly.
- Mark only the scenarios you want in regression as Include in suite; keep one-off variations out of the fan-out.
- Keep a sensible default so an ad-hoc run does something useful with no selection.
- When you rename or remove a workflow input, revisit each scenario so its values still line up.