> ## Documentation Index
> Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Run the full suite

> Run every active Qodex scenario and scenario group in the project from any trigger surface.

# Run the full suite

The full suite run is the broadest Qodex run scope. It includes every active scenario and scenario group in the project, then writes all results to one test run.

Use it for nightly regression, pre-release validation, or any moment when you want the complete current picture.

## What runs

Qodex includes:

* Active standalone scenarios.
* Active scenario groups.
* Runnable API scenarios with compiled scripts.
* Runnable UI scenarios with recorded steps.

Qodex skips drafts and unrunnable scenarios. Drafts stay out of full-suite runs so unfinished agent output does not break scheduled or CI checks.

## How execution works

Standalone scenarios run in parallel within the project's concurrency limits. Scenario groups run as one unit, using the mode saved on the group.

Sequential groups run members in order. If a member fails and stop-on-failure is enabled, later members in that group iteration are skipped, but other standalone scenarios and other groups continue.

Parallel groups run members independently at the same time. They do not share captures between members, and stop-on-failure does not apply.

| Unit                       | Behavior                                             |
| -------------------------- | ---------------------------------------------------- |
| Standalone scenario        | Runs independently.                                  |
| Sequential group           | Runs members in order and can share captured values. |
| Parallel group             | Runs members independently at the same time.         |
| Failed sequential member   | Can stop the rest of that group iteration.           |
| Failed standalone scenario | Does not block other scenarios.                      |

## Run from the web app

Open **Scenarios**, clear filters, then click **Run all**. Choose the environment and start the run.

The button uses server-side matching, so you do not need to select every row manually.

## Run from CI or webhook

Send a project trigger without tags:

```bash theme={null}
curl -X POST \
  https://agents.qodex.ai/api/projects/my-project-slug/webhooks/trigger \
  -H "Authorization: Bearer qk_xxx..." \
  -H "Content-Type: application/json" \
  -d '{"environment":"staging"}'
```

No `tags` field means Qodex runs the full active suite.

## Schedule the full suite

Create a schedule with run type **All active scenarios**. This is the common shape for nightly or weekly regression.

## Related

<CardGroup cols={2}>
  <Card title="Run tests on a schedule" icon="calendar-clock" href="/run-tests-on-schedule">
    Run the full suite automatically.
  </Card>

  <Card title="Re-run failed tests" icon="rotate-ccw" href="/run-tests-rerun-failed">
    Focus on failures after a broad run.
  </Card>

  <Card title="Test groups and folders" icon="folder" href="/run-tests-test-groups-and-folders">
    Understand how grouped scenarios behave inside suite runs.
  </Card>
</CardGroup>