Abort Tests

You can abort running tests and in-progress test flow setups at any time. Instead of waiting for a stuck or misconfigured test to finish, cancel it immediately and move on.

Aborting a Running Test

When a test is actively running, a red Abort Test button appears in the test details page header. The button is visible when the test status is Created (queued) or Started (actively running).

After clicking Abort, the test transitions to Pending Abort status. You’ll see the message: “You sent a request to abort this test. Please wait for the request to be processed.” The system finishes its current operation and then marks the test as Aborted.

Aborting Test Flow Setup

If a test flow is being set up (step generation, preview testing), you can abort the setup process from the test flow page. The Abort Setup button appears during the setup phase.

What You Cannot Abort

Tests in Awaiting Email status cannot be aborted. These tests have completed execution and are waiting for an email delivery confirmation from the background verification process. The email check runs for up to 2 hours before timing out automatically.

Stuck Tests

CheckView automatically detects tests that appear to be stuck and force-aborts them. You don’t need to manually intervene for tests that hang indefinitely – the system handles this automatically.

Test History

Aborted tests are tracked in your test run history with an Aborted status badge. They are separate from failed tests and don’t trigger failure notifications.

Aborting via API

You can also abort tests programmatically using the REST API. Use PATCH /api/v1/test-runs/:id to abort a single test, or PATCH /api/v1/test-runs for bulk abort (up to 50 tests at once). See the REST API Endpoint Reference for details.