> ## 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 tests from the web app

> Start a Qodex run from the browser, choose the scope and environment, and watch results stream live.

# Run tests from the web app

The web app is the fastest way to run Qodex scenarios by hand. Use it when you want to check a new scenario, run a smoke set after a deploy, or inspect failures without leaving the product.

You can run one scenario, selected rows, a filtered set, or the full active suite. Every run writes to the same test run history.

## Before you start

Make sure the project has:

* At least one runnable scenario.
* An environment such as `staging`, `prod`, or `preview`.
* Any variables, base URLs, and auth profiles required by the selected scenarios.

API scenarios need compiled script content. UI scenarios need recorded steps.

## Run one scenario

Open **Scenarios**, click the scenario you want to test, then click **Run**.

Choose the environment in the run dialog. For UI scenarios, you can also enable video recording when you need a shareable reproduction.

## Run a filtered set

Use filters in the scenario list to narrow by tag, type, priority, status, or last run outcome. Then click **Run all**.

Qodex runs the full filtered result set, not just the rows visible on the current page. This is useful for tags such as `smoke`, `critical`, `security`, or `regression`.

## Run selected rows

Tick the scenarios you want, then click **Run selected**. Use this when the set is ad hoc and does not deserve a permanent tag.

## Run a group or folder

Switch to **Scenario groups** when related scenarios should run together. Click **Run group** to start the whole group against the selected environment.

Sequential groups run members in order. Parallel groups run members independently at the same time. UI-only groups also show **Record**, which captures video for each UI scenario in the group.

## Watch the run

After you start the run, Qodex creates a test run and opens the run detail page. As scenarios execute, you can see:

* Step status and assertion text.
* API request and response evidence.
* UI screenshots and failure artifacts.
* Live stdout and stderr for script execution.
* Aggregate pass and fail counts.
* Findings created by failed scenarios.

You can leave the page and come back later; the run continues in the background.

## Draft behavior

Scheduled runs skip draft scenarios. Manual runs from the web app honor your explicit selection, so drafts can run when you choose them directly.

## Related

<CardGroup cols={2}>
  <Card title="Run a single scenario" icon="play" href="/run-tests-single-scenario">
    Replay one scenario end to end.
  </Card>

  <Card title="Run tag-filtered scenarios" icon="tag" href="/run-tests-tag-filtered">
    Run a saved group of scenarios by tag.
  </Card>

  <Card title="Test groups and folders" icon="folder" href="/run-tests-test-groups-and-folders">
    Learn when to use groups instead of selected rows.
  </Card>
</CardGroup>