TestRunEXecute

TREX catches the bugs that only show up at runtime. It starts your services, sends real requests, exercises the changed code, and leaves the logs, screenshots, and traces on the PR.

contact sales get started

no credit card required • 14-day free trial

[ TREX ]

How TREX validates a PR

How it works

Understands the change

TREX looks at the PR, your repo, your test suite, and your stack to figure out what needs to run.

Runs it in a sandbox

TREX installs your dependencies, starts the services the change touches, and exercises the code with targeted tests.

Shows what broke

When a run fails, TREX traces it back to the relevant code and leaves a PR comment with the evidence attached.

[ TREX ]

Get the bugs you can't find by reading the diff

Greptile with TREX catches ~20% more bugs than review alone. Those are the bugs that only show up when the code runs.

Evidence on every finding

TREX does not just say something failed. It shows what happened with logs, screenshots, traces, scripts, videos, or API output attached to the PR comment.

Works with your stack

TREX runs against the dependencies, frameworks, and test setup your repo already uses.

Tests end to end

TREX mocks inputs, spins up dev servers, and uses browser agents to click through your UI.

[ TREX EXAMPLES ]