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

# Failed vs finding

> A fail is a result on a run. A finding is the issue you file (bug/defect) with severity, status, and evidence.

Easy to mix together because both are "it didn't work."

## Fail

A **result**. This case or step, on this run, did not meet expected. Buttons: **Fail**. Case result `failed`. Step `fail`.

Fails are how coverage math and the cycle look honest. A fail without a finding is "we saw it fail" without a ticket. Sometimes that's OK (you blocked on env and don't want a bug). Usually, for client-facing bugs, file the finding.

## Finding

An **issue record** on **Findings**. Severity, status, priority, comments, evidence, optional Jira link. Standalone **Log a finding** is allowed. Fail-step can prompt **file issue**.

That's the bug tracker row / the email to the PM.

## Rule of thumb

* Scripted check didn't match expected to **Fail** the step/case.
* Someone should fix or accept a defect to **Finding**.
* You couldn't run it to **Blocked**, maybe no finding.
* Out of scope this cycle to **Skipped**.

[Findings overview](/findings/overview), [Pass/fail/blocked](/running/pass-fail-blocked)

<Columns cols={2}>
  <Card title="Log findings" icon="bug" href="/playbook/bugs">
    Fields and evidence.
  </Card>

  <Card title="Retest" icon="rotate-ccw" href="/findings/retest">
    After a fail or client request.
  </Card>
</Columns>