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

# Running the work

> Use cycles as the testing round and runs as execution. Mark pass, fail, blocked, and N/A as you go.

You used to highlight rows. Now you **Start a run**. Same process, durable results.

## Cycle = the round

A cycle has status `draft` | `active` | `in_progress` | `completed` | `archived`, plus title, description, environment, dates, and `case_ids`. It's the "UAT week 2" tab. You don't execute inside the cycle list; you start a run from it.

## Run = you clicking through

Run status: `in_progress` | `completed` | `aborted`. Case results: `passed` | `failed` | `blocked` | `skipped` | `in_progress`. You need an **active tester** (assignment) to start.

If start is disabled: [can't start](/troubleshooting/cant-start).

## Cadence that works for jobs

1. Scope the cycle to what you quoted, not every optional pack case.
2. Record results as you test, not later. Evidence is easier in the moment.
3. Fail + finding when it's a product bug. Blocked when you can't execute (no data, env down). Skipped when out of scope. N/A on a step that doesn't apply. [Meanings](/running/pass-fail-blocked).
4. Complete or abort the run honestly. Aborted is better than a fake 100% pass.

Exploratory still counts: thin cases plus **Log a finding**. [Exploratory](/running/exploratory).

<Columns cols={2}>
  <Card title="Pass, fail, blocked" icon="check-square" href="/running/pass-fail-blocked">
    Buttons vs case results vs skipped.
  </Card>

  <Card title="Log bugs while you run" icon="bug" href="/playbook/bugs">
    Findings, evidence, Jira links.
  </Card>
</Columns>