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

# Exploratory testing

> Use lightweight cases, standalone Log a finding, and evidence when you are not following a heavy script.

Exploratory is still testing you already know how to do: poke the new checkout, take screenshots, write down bugs. SimpleUAT doesn't need a 40-step case for that.

## Lightweight cases

One case per charter is enough: "Explore promo + guest checkout on mobile width." Preconditions: build URL, persona. Two or three steps ("explore X", "note issues"). Run it so the cycle shows you worked. Don't fake 15 passes.

## Standalone findings

**Log a finding** is allowed without a failed step. That's the bug list from a session. Attach evidence (25MB, images/pdf/video). Link the finding in comments to the run if you want a written record.

## Evidence is the session notes

There is **no session recording** product. Your WebM/MP4 or screenshots *are* the recording. Put them on the finding or the step.

## When to switch back to scripts

If the client paid for regression sign-off, use real cases (or a pack). Exploratory-only is a weak delivery snapshot for "we tested everything." Mix: smoke pack + exploratory charters + findings.

<Columns cols={2}>
  <Card title="Evidence types" icon="paperclip" href="/findings/evidence">
    Formats and size limit.
  </Card>

  <Card title="Log findings" icon="bug" href="/findings/overview">
    Severity, status, standalone log.
  </Card>
</Columns>