For the complete documentation index, see llms.txt. This page is also available as Markdown.

Start a Run

Start a single Flow, a Test Pack, a Recipe, a Schedule, or a CI/CD Run.

You can start a Run from a single Flow, from several Flows at once, on a timetable, or from CI/CD. Choose the path that matches how often and how wide the coverage should be.

Run one Flow

Where
Control
What it does

Flows list

Run Flow

Starts that Flow

Flow Builder toolbar

Run Flow

Starts the Flow you are editing

Scenario toolbar

Run or Run Tests

Starts the Flow from the Scenario editor

Scenario or Results

Preview Tests

Builds a preview without a normal live Run

After a Flow Run starts, DoesQA opens that Flow’s Results tab. See Understand your results.

Run a Test Pack

A Test Pack is a Run you start yourself across one or more Flows.

  1. Open Flows.

  2. Choose Run Test Pack. The dialog title is Start Run.

  3. Set Flow Filters and Test Case Filters with Include Tags and Exclude Tags when you want a subset.

  4. Optionally paste Value Overwrites for this Run.

  5. Choose Run.

Tag filters follow the same rules as Run Recipes. Value overwrite order is on Value Store.

Run a Recipe

Run Recipes save filters and Value Overwrites you reuse.

  • On Flows, open Run Recipes and pick a recipe.

  • Or go to Settings → Run Recipes and choose Run Recipe on a row.

Schedule a Run

Create a Schedule under Settings → Schedules (or from the Flows menu) when the same pack should start on a timetable. Point the Schedule at tags or a Recipe.

Start from CI/CD

Use the webhook under Settings → CI/CD so a pipeline can start a Run. See Trigger Runs from CI/CD.

Start a child Run from a Flow

Add DoesQA Run when one Flow should start another Run during execution. See Reuse a login session for a common pattern.

Last updated