Skip to main content
A Case is a saved state of value configuration for a journey — for example, “Happy path”, “Missing funding source”, or “Expired token”. Instead of re-entering the same values every time you run, you select a case and Reqflo autofills the value configuration. Cases keep your testing intentional and repeatable.

​
When to use it

  • You have a set of values that represent a meaningful test scenario and want to save them for repeated use.
  • You want to quickly switch between scenarios (happy path, edge case, error state) without reconfiguring values manually.
  • You’re sharing a journey with teammates and want to give them pre-built configurations to run from.
Cases are useful in the editor, Run mode, Runbooks, and the CLI — the same saved configuration works across all of them.

​
Key concepts

  • Case — a named snapshot of value configuration. Selecting a case autofills all values it defines; any values not covered by the case remain at their current setting.
  • Save — you can save the current value state as a new case or overwrite an existing one.
  • Rename / duplicate / archive — cases can be renamed, duplicated (to create a variation), or archived when they’re no longer active. Archived cases can be restored.
  • Cases vs. environments — a case describes the data (what values you’re running with); an environment describes the system target (which servers you’re hitting). They’re separate and combine at run time.
  • Cases vs. overlays — cases handle value variation within the same journey definition. Overlays modify the journey structure itself (steps, assertions, configuration). Use cases for data variation; use overlays for structural variation.
A pinned or default case — one that pre-selects automatically — may be introduced in a future update. For now, you select a case manually.

​
How it works

Saving a case: Configure your values in the Values panel or during a run, then open the case selector and choose Save as case. Give the case a name that describes the scenario. Selecting a case: Open the case selector (available in Build mode, Run mode, Runbook, and CLI) and pick the case you want. The value configuration is applied immediately. Managing cases: From the case list, you can rename, duplicate, or archive any case. Archived cases no longer appear in the active list but can be restored if needed.

​
Examples

A payment journey might have three cases:
Case nameScenario
Happy pathValid card, sufficient funds, correct billing address
Declined — insufficient fundsValid card details but balance below the charge amount
Expired tokenAuth token set to an expired value to test 401 handling
Each case saves the full value configuration for that scenario. Switching between them takes one click. Using a case from the CLI: 
reqflo run payments/checkout --case "Happy path" --env staging

Cases concept

The mental model behind cases and how they fit into the product.

Environments

Choose the system target — separate from case configuration.

Values panel

Configure the values a case saves.

CLI: run with a case

Use cases in CLI commands.