Step-specific failure reasons

We're continuing to release a series of improvements to the test output page.

Now, when you view the output for a failed test you'll see step-specific failure reasons in the list of steps on the left side of the page.

With these clearly stated failure reasons, you'll be able to more quickly determine why a test failed and what your next steps toward debugging the test might be.

Failure Categories

The step-specific failure reasons cover the following failure categories. In some cases, it may be necessary to dig a little deeper by reading through the activity logs.

• Assertion not met
• Could not click and hold element
• Could not click element
• Could not double click element
• Could not enter text
• Could not open email
• Could not open tab
• Could not select
• Could not send keypress
• Could not visit URL
• Element not found
• Email not found
• File not found
• Frame not found
• Generation failed
• JavaScript step failed
• Tab not found
• Wait failed
• Window not found

If a failure reason does not fall into the above categories, it will be labeled as "Other error". Reading the activity logs for this step may help you determine the reason for the failure.

In some cases, errors will occur that mabl is unfamiliar with. If that happens, the error will be labeled "Unknown error". Reading the activity logs for this step may help you determine the reason for the failure.

Failed Assertion

If an assertion fails, the failure reason will tell you the value mabl was expecting to find, and what value was actually found.