When viewing the test output for a specific run, you can use the step filter to quickly identify issues, such as "Warning," "JS Exception," and "Error," and get a better understanding of your test. This guide explains how to filter test steps and what the different types of filters mean.
How to filter steps
To filter test output, take the following steps:
- Navigate to the test output page for the test run you want to review.
- Click on the "Filter" bar to open the filter dropdown.
- Select a filter from the dropdown. Alternatively, type your own custom filter, such as "loader," "fire," or anything you'd like. The filter uses word stemming to be able to filter additional words that may be relevant, such as "load" from a "loader" filter.
Filtering test output
Mabl shows the relevant steps after a filter has been applied.
Types of filters
The following table outlines the types of filters available and what they mean.
|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.
|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.
|Mabl identified accessibility violations during the accessibility check.
|Mabl detected a visual change between the screenshot of the current test run and the original baseline test.
|Mabl could not find a strong match to the target element and identified the best candidate element using the element history.
|The test step passed.
|The test step is neither a failing nor a passing test step. Steps classified as "info" include steps that start and end a flow.