> ## Documentation Index
> Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Results

> Read the TREX comment on a pull request and watch the recording behind each result.

## The TREX comment

TREX posts a **TREX** comment on the pull request (or merge request) next to the review. While it runs, the comment shows its progress. When it finishes, the comment shows the results:

```markdown theme={}
## TREX

Tested 2 flows, found 1 issue. Faced 1 blocker.

### Findings
- [P1] Saved state is lost after reload ▶

### Blockers
- The app could not start because DATABASE_URL was missing.

To unblock, configure your TREX environment.

### What we tested
- **Pass** — Open the project list ▶
- **Fail** — Rename a project ▶
```

Empty sections are left out.

| Section | What it means |
| - | - |
| **Findings** | Bugs TREX saw, with a severity (P0 to P2). When a finding maps to a line in the diff, TREX also leaves an inline comment. |
| **Blockers** | What stopped TREX from testing, such as a missing variable or a service that didn't start. The link opens your [environment](/docs/trex/environments). |
| **What we tested** | Flows with at least one passed or failed check, in the order **Pass**, **Fail**, **Incomplete**. A failed flow with unfinished checks shows **Fail (testing incomplete)**. |
| **Incomplete custom user flows** | [Custom flows](/docs/trex/custom-flows) TREX couldn't set up or whose checks look wrong, each with an **Edit flow** link. |

"No flows tested" means TREX couldn't test anything. It is not a pass; check **Blockers**.

If TREX needed more than one attempt, the comment says so. It retries after fixing its own setup, for example when a service didn't start the first time.

**▶** opens that flow in the pull request's **TREX** tab in Greptile.

## Watch a flow

The pull request's **TREX** tab in Greptile lists every tested flow. Open a flow to see its steps on the left and the recording on the right.

![The TREX tab of a pull request with one flow open](https://mintcdn.com/greptile/uh7ZNTHIRsgxy_lm/images/trex-flow-evidence.png?fit=max\&auto=format\&n=uh7ZNTHIRsgxy_lm\&q=85\&s=f8700c29df62e815437cca4b7674b627)

* **Steps**: numbered steps and the checks under each one, with what TREX observed. Each check shows its outcome:
  * a severity badge (`P1`, `P2`): the check failed and produced a finding,
  * ✓ passed,
  * ⚠ blocked, with the reason,
  * greyed out: not attempted.
* **Recording**: a video of TREX using your app, with captions for what it's doing. Steps are marked as chapters on the timeline. Selecting a step or check jumps to that moment.
* Use **↑** and **↓** to move between flows, and **↔** to widen the view.

Selecting a step or check updates the URL (for example `?step=2&check=1`), so you can share the exact moment.

![A selected failed check with its P1 finding](https://mintcdn.com/greptile/uh7ZNTHIRsgxy_lm/images/trex-flow-evidence-check.png?fit=max\&auto=format\&n=uh7ZNTHIRsgxy_lm\&q=85\&s=165f5809c028b1fd938291be2aac22e0)

## Access and retention

* Viewing a recording needs read access to the repository in Greptile. On public GitHub.com and GitLab.com repositories, anyone with the link can view it.
* Recordings and other evidence are kept for 30 days.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.