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

# Pass, fail, blocked, N/A

> How to mark steps and cases so results match what you would have put in a spreadsheet.

Mark what happened.

## Step buttons

* **Pass:** this step did what `expected_result` said
* **Fail:** it didn't. File a finding when it's a product defect (the UI can prompt **file issue**)
* **Blocked:** you cannot complete the step (VPN, no OTP, env 500)
* **N/A:** step doesn't apply (`not_applicable`). Example: PayPal step on a store that only has cards

Unmarked is **not\_run**. Finish or skip the case so reports don't look unfinished unless they are.

## Case results

`passed` | `failed` | `blocked` | `skipped` | `in_progress`

**Skipped** = not executing this case in this run (out of quote, feature flagged off). That's not N/A.

## Mapping from the sheet

* Green to pass
* Red to fail (+ finding)
* Orange "can't test" to blocked
* Gray "not this sprint" to skipped
* "n/a" on a step to N/A

More concept detail: [statuses](/concepts/statuses), [failed vs finding](/concepts/failed-vs-finding)

<Columns cols={2}>
  <Card title="Runs" icon="play" href="/running/runs">
    Starting and finishing.
  </Card>

  <Card title="Findings" icon="bug" href="/findings/overview">
    When fail becomes an issue.
  </Card>
</Columns>