> ## 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

> Run Qodex scenarios on demand, on a schedule, through webhooks, or in CI against any configured environment.

# Run tests

Once a scenario is saved, Qodex can replay it from the web app, a schedule, a webhook, or your CI pipeline. The same test run view collects the result, step output, artifacts, and findings no matter where the run started.

This gives teams one place to run smoke checks, nightly regressions, security checks, UI flows, and API suites against staging, production, preview, or any other named environment.

## How running tests works

The run flow has four parts:

* **Choose a trigger** such as manual run, schedule, webhook, or CI.
* **Choose a scope** such as one scenario, a test group, a tag-filtered set, failed scenarios, or the full active suite.
* **Choose an environment** so the same scenario can run against staging, production, or a preview target.
* **Review results** in the test run detail page, with failures classified as real bugs, stale tests, or environment issues.

API scenarios replay as executable scripts. UI scenarios replay through Chromium and Playwright using their recorded steps and cached actions. Repeat runs do not need the agent to regenerate the scenario.

## Pick how the run starts

<CardGroup cols={3}>
  <Card title="From the web app" icon="mouse-pointer-click" href="/run-tests-from-web-app">
    Start a run manually and watch results stream in the browser.
  </Card>

  <Card title="On a schedule" icon="calendar-clock" href="/run-tests-on-schedule">
    Run smoke, regression, or security checks on a recurring cadence.
  </Card>

  <Card title="Via webhook" icon="webhook" href="/run-tests-via-webhook">
    Trigger a run from CI, deploy scripts, or any external system.
  </Card>
</CardGroup>

## Pick what runs

<CardGroup cols={3}>
  <Card title="Single scenario" icon="play" href="/run-tests-single-scenario">
    Replay one scenario against a chosen environment.
  </Card>

  <Card title="Tag-filtered scenarios" icon="tag" href="/run-tests-tag-filtered">
    Run every active scenario with tags such as smoke, regression, or security.
  </Card>

  <Card title="Test groups and folders" icon="folder" href="/run-tests-test-groups-and-folders">
    Run related scenarios as one sequential flow or parallel folder.
  </Card>

  <Card title="Full suite" icon="list-checks" href="/run-tests-full-suite">
    Run every active scenario and scenario group in the project.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Re-run failed tests" icon="rotate-ccw" href="/run-tests-rerun-failed">
    Replay a previous run or isolate scenarios that failed most recently.
  </Card>

  <Card title="In CI" icon="git-branch" href="/run-tests-in-ci">
    Gate merges and deploys with Qodex runs from your pipeline.
  </Card>
</CardGroup>

## What results include

Each run writes to the same test run model:

* Overall status and per-scenario status.
* Step-level pass, fail, and skipped results.
* API request and response evidence.
* UI screenshots and failure artifacts.
* Failure classification for broken scenarios.
* Findings created from confirmed product, security, or environment issues.

## Where to go next

<CardGroup cols={2}>
  <Card title="Run tests from the web app" icon="mouse-pointer-click" href="/run-tests-from-web-app">
    Start with the easiest manual run path.
  </Card>

  <Card title="Run tests in CI" icon="git-branch" href="/run-tests-in-ci">
    Add Qodex as a required check in your release workflow.
  </Card>
</CardGroup>

## On the roadmap

<Tip>
  Skill-typed scheduled runs, SARIF and JUnit XML export, and Slack, email, and webhook delivery of run results are tracked on the Qodex roadmap.
</Tip>