This article lists all the possible statuses for mabl test runs. For information on plan run statuses, see the article on plan run output.
Starting
mabl is acquiring the resources to start running the test.
Running
The test run is in progress. When a browser test has a "running" status, you may watch the results live.
Passed
The test run completed with all passing steps.
The following test steps can be configured to pass even if the step lacks "passing criteria":
- Assertions marked "continue on failure"
- Accessibility checks marked "never fail"
The only way to determine if these steps passed is to review the test output. If these steps fail, they are marked as "Passed with warning."
Failed
The "failed" status appears for test runs that failed to pass at least one step in the test.
Failure by webhook response
If your workspace is configured to post information to a webhook and receive a successful response before executing tests, the failed status also appears for tests that received an unsuccessful webhook response.
Stopped
The "stopped" status appears in the following circumstances:
- The test run reached the maximum run time before completing all steps.
- A member of the workspace stopped the test before it finished running.
Maximum run times
The maximum run times for cloud runs are as follows:
- Browser tests: six hours
- Mobile tests: one hour
- API tests: 30 minutes
Skipped
In plan runs, a "skipped" status indicates that the test was scheduled to run, but an earlier test in the plan run failed or stopped running. This behavior is the default for plan runs. To update a plan's behavior on failure, edit plan stage settings.
Waiting
The "waiting" status appears for tests in plan runs that are waiting for a sequential test or stage to pass.
On hold
The "on hold" status indicates that your workspace has reached the rate limit of allowed concurrent test runs.