Skip to main content

Running tests

Run the trq CLI from your project folder (the folder that holds your .trq files). List what's there any time:

trq list

One test​

trq play checkout          # headless (no window)
trq play checkout --headed # show a real browser window

Handy while debugging:

  • --to N — stop after step N.
  • --slow — replay at a human pace so you can follow along.

A whole folder​

Point Trq at the current folder and run everything in it:

trq play --sequential              # one test at a time
trq play --parallel                # several at once (auto-sized to your machine)
trq play --parallel --workers 4    # cap the number of parallel workers

A suite​

Run a saved suite by name — it uses the suite's own sequential/parallel mode unless you override it:

trq play --suite smoke

Against an environment​

Swap base URLs, credentials, and other {{env.*}} values per environment:

trq play checkout --env staging
trq play --suite smoke --env production

Pass or fail​

Every run prints a summary and exits with a standard code:

  • 0 — all tests passed.
  • 1 — at least one test failed.

That's what lets a build pipeline turn green or red automatically. To also write a machine-readable report (JUnit / JSON), see In CI.