- Figures out which user flows your changes affect.
- Starts your app in a sandbox built from your environment.
- Uses the app like a user would: clicking, typing, and observing what’s on the screen.
- Posts what it tested and what broke, with a video of every flow.
Getting started
1
Turn on TREX for your organization
Open Settings → Agent Config → TREX → Settings and Enable TREX.
2
Set up an environment
Tell TREX how to set up and build all the dependencies that allow it to run your services. See Environments.
3
Open a pull request
TREX runs with the next review and posts a TREX comment.
Pricing
A TREX run will cost 3 credits. This is distinct from the cost of the code review. Check out Billing for more information. Runs that do not have complete user flows tested will not be charged.When TREX runs
Once Enable TREX is on, choose When TREX runs:
A rule is a set of conditions such as branch, labels, authors, or file paths. All conditions in a rule must match. Rules inherited from a parent namespace show read-only under yours.
Automatic TREX runs sets which pull request events start TREX, the same way it works for reviews.
TREX also decides on its own when a pull request has nothing to test. For example, a change with no effect on how the app behaves. It skips testing, says why in its check, and doesn’t charge credits.