Skip to main content

​
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:
Empty sections are left out. “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
  • 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

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