> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/runs/start-a-run.md).

# Start a 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](/getting-started/understand-your-results.md).

## Run a Test Pack

A [Test Pack](/getting-started/terminology.md) 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](/configuration/run-recipes.md). Value overwrite order is on [Value Store](/values/value-store.md).

## Run a Recipe

[Run Recipes](/configuration/run-recipes.md) 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](/configuration/schedules.md) 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](/configuration/ci-cd.md).

## Start a child Run from a Flow

Add [**DoesQA Run**](/test-steps/express/doesqa-run.md) when one Flow should start another Run during execution. See [Reuse a login session](/guides/reuse-a-login-session.md) for a common pattern.

## Related

* [Runs](/runs/runs.md)
* [Run History and Run detail](/runs/run-history-and-detail.md)
* [Run Recipes](/configuration/run-recipes.md)
* [Schedules](/configuration/schedules.md)
* [Build smoke and regression coverage](/better-coverage/build-smoke-and-regression-coverage.md)
* [Run across environments](/better-coverage/run-across-environments.md)