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

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

Test every change end to end

TREX spins up the services your change touches and uses computer use to test them. It clicks through desktop apps, web apps and command-line tools the way a real user would.

Get started