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

# Test runs

> Start a run from an active cycle with an assigned tester. Record case results and complete or abort the run.

A **run** is you executing the cycle's cases. Same idea as coloring the result column, except it doesn't destroy last week's colors.

## Before you click Start a run

* Cycle exists and includes `case_ids`
* Environment on the cycle
* At least one **active tester** (you, on **Assignments**)
* Cases are actually `active` and selected

Otherwise: [can't start](/troubleshooting/cant-start).

## During

Open the case. Follow steps. **Pass / Fail / Blocked / N/A**. Attach evidence when the step asks or when you'd have attached a screenshot to email anyway.

Run status stays `in_progress` until you complete or abort. Case-level: `passed` | `failed` | `blocked` | `skipped` | `in_progress`.

Some UIs say **Launch Quick Run**. Same idea as **Start a run**, different copy. Use whichever button you have.

## After

**Completed** = you finished the set. **Aborted** = you stopped (bad build, wrong env). Don't mark everything passed to close the run.

Retest = new run, same cycle or a new cycle. Old run stays as history.

<Columns cols={2}>
  <Card title="What the buttons mean" icon="check-square" href="/running/pass-fail-blocked">
    Pass, fail, blocked, N/A, skipped.
  </Card>

  <Card title="Exploratory" icon="compass" href="/running/exploratory">
    Thin cases plus standalone findings.
  </Card>
</Columns>