When viewing test output for a specific run, use the step filter to quickly identify issues and get a better understanding of your test. You can use the preset filter types, such as "Warning," "JS Exception," and "Error," or create your own custom filter to search for steps with matching keywords.
This article explains what the different types of filters mean.
Filtering test output
Types of filters
The following table outlines the types of filters available and what they mean.
| Filter | Description |
|---|---|
| Error | The test step failed. Common reasons for failed test steps include network timeouts, server errors, and failure to find an element that matched the target element criteria. |
| Warning | mabl encountered non-working elements when executing the test step, such as network request errors or failed assertions that use the "continue on failure and mark warning" option. |
| JavaScript exception | mabl detected a Javascript error on the page and logged the type of error encountered as well as the page and source, if applicable |
| Accessibility violation | mabl identified accessibility violations during the accessibility check. |
| Visual change | mabl detected a visual change between the screenshot of the current test run and the original baseline test. |
| Auto-heal | mabl could not find a strong match to the target element and identified the best candidate element using the element history. |
| Success | The test step passed. |
| Info | The test step is neither a failing nor a passing test step. Steps classified as "info" include steps that start and end a flow. |