Skip to main content

Running a case

A Send fires one request. Run replays the whole session as a test case — every request, top to bottom, with variables flowing down the chain — and reports a single verdict.

A running case — the executing request is highlighted live, with a Stop button in the toolbar

The Requests panel​

Requests live in the Requests tab of the bottom dock panel — the same shared panel as web and mobile, with the same shortcuts (⌘J toggle, ⌘D dock left/right, focus mode). Each row shows its index, method, name, and — after a run — its pass/total and timing.

  • ＋ Add request (top-right of the panel) appends a new request.
  • Double-click a row to rename it — named steps make the report readable.
  • Reorder requests to control execution order; they run in list order.

Run​

Press ▶ Run in the toolbar. Trq executes each request in turn:

  • The currently executing request is highlighted live — an accent bar and a spinner — and the highlight moves down the list as each finishes.
  • The request/response panes refresh to the executing request, so you watch real responses stream past.
  • Variables extracted by one request are available to the next (see chaining).
  • The status bar flips to orange REPLAYING while the case runs, exactly like a web or mobile replay.

Stop​

Click ■ Stop (it replaces Run while a case is executing) to cancel mid-flight — useful when an early request is clearly wrong and you don't want to wait out the rest.

Fail-fast​

A case runs in order and reports every request's result. When you need the same case on a build server — with an exit code instead of a panel — run it from the trq CLI.

Next: read the run report, or wire it into CI.