Skip to main content
A Backend project test list, the starting point for any rerun

​
Three Rerun Surfaces

Auto-Heal is UI-only, because UIs drift in ways HTTP APIs don’t. For API tests, Auto-Auth is what keeps long-running schedules healthy by keeping tokens fresh.

​
Single Test Rerun

From a test’s detail page, click Run test.
Rerunning one API test from its detail page
Most API tests consume variables from earlier tests in a chain. A normal rerun re-runs the producers first, getting fresh captures, then runs the consumer.

​
Rerun All (Batch)

On the project’s test list, Run all (top right) re-executes every test in the project.
Run all on the Test Cases toolbar, queueing every test in the project

​
Scheduled Reruns

Schedules run on a cadence (hourly, daily, weekly, monthly). For API projects, each scheduled run rebuilds every chain, uses Auto-Auth when it’s configured, and ends with Auto Cleanup so it leaves a clean environment. Set one up in Test Schedules.
A schedule's page: execution trend, breakdown, and previous executions

​
What Happens to Cleanup on Rerun

Every rerun (single, batch, or scheduled) ends with Auto Cleanup. The DELETE chains are rebuilt from the records the rerun created, not the previous run’s.

​
Cascading: Rerun a Producer = Rerun Its Consumers

Rerunning a producer automatically reruns the tests that consume its variables, with the fresh values:
  • Rerunning POST /users (a producer) → automatically reruns POST /orders, GET /orders/, DELETE /orders/
  • Rerunning DELETE /orders/ (a leaf consumer) → only that test reruns; its upstream stays as-is
See Dependency Chains for how producer/consumer relationships are identified.

​
Rerun Outcomes

After a rerun, the test row shows the new outcome. The previous run is kept under Test Runs, so you can compare the two.

​
Edge Cases & Troubleshooting

The producer you reran feeds many consumers across chains. To re-execute just one consumer, open that test and rerun it directly.
Its producers depend on further upstream tests. A deep chain can make even a leaf test’s rerun take several minutes.
Usually one of: a real flake in your API, captured state that changed between runs (a record was modified), or an auth token that expired between runs (use Auto-Auth).
The test is probably still Queued or Running. Wait until it shows Passed or Failed.

​
Where to Go Next

Dependency Chains

Understand cascade order

Auto-Auth

Token refresh keeps reruns alive

Insights

Regressions and quality trends across runs

Test Schedules

Set up automated reruns on a cadence