> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qa.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qa.army/_mcp/server.

# Results and Evidence

> Understand test results and the evidence available for each run.

## Result meanings

* `PASSED`: every required assertion succeeded.
* `FAILED`: the journey ran and a product assertion failed.
* `ERROR`: QA.army could not determine a reliable product result.
* `CANCELLED`: the Run stopped before completion.

Use `FAILED` for a reproducible product problem. Use `ERROR` when setup, access, execution, or evidence prevents a reliable conclusion.

## Evidence

Evidence helps your team understand and reproduce a result. Depending on availability, a Run can include:

* step and assertion timing;
* screenshots and recordings;
* console and network activity;
* environment details;
* reproduction steps.

Only authorized Workspace members can open evidence. Never include passwords, access tokens, or real customer data in Test steps or fixtures.

Web Runs can include recording-based evidence. Open the artifacts available for
the specific Run; missing evidence does not imply a pass. See
[Recordings](/recordings) for playback and sharing guidance.