Skip to main content
Run your tests whenever you want to check your API’s health. You can run everything at once or a single suite, and every run produces a detailed report.

​
Start a run

On the API Tests page:
  • Run Suite runs every suite that isn’t archived.
  • Run on an individual suite runs just that one.
Run controls on the API Tests page
Starting a run takes you to the API Test Runs page, where the run appears as it executes.
API Test Runs page

​
Read a run report

Open a run to see the full report. The header summarizes the run: its branch, start time, duration, and environment, with Passed, Failed, and Bugs totals. Results are grouped by suite, each showing its passed/failed counts. Click into a case to see its journey, steps, and assertions, any error message, and the HTTP calls it made. For every call you get:
  • the HTTP method and path that was called,
  • the status code it responded with (green under 400, red at 400+), and
  • how long the call took, in milliseconds.
Guided tour of a run report: journey/steps/assertions, each API call's method and path, and its status code and timing
The per-call timing makes it easy to spot which endpoint is slowing your product down; scan the slow steps to find latency regressions.
A case with many calls shows the first 20, then a ”+ N more calls (truncated)” note.

​
Run statuses

​
What a run can and can’t tell you

A run executes your tests and reports exactly what happened, but it leaves the judgment calls to you and the agents.

​
When a test fails

If a run surfaces a failing test or a suspected bug, it flows to the API Triage board, where you confirm bugs, dismiss false positives, and trigger healing. The run report also links directly to the healing session when one is started for the run.

​
Next Steps