After individual test cases are run, the results are viewable in the Test Results page in the Mesmer console. Click the Test Results link at the top of the console to navigate there. This page shows a summary of all available test results. Each test result is represented by a card that shows the title of the test case and a status indicator.
Over time, you might accumulate hundreds of test cases with results. You can make use of filtering options to view only the test cases of specific interest. There are several aspects of filtering you can apply to the results.
The status filters on the left (All, New, Passed, Failed, Needs Review, and Broken) are each mutually exclusive - you can have only one selected at a time.
All: remove status filtering and show all results
New: test results that were part of the last test run
Passed: test results that fully passed
Failed: test results that had some failure, marked in red (e.g. a crash)
Needs Review: test results had some unexpected anomaly, marked in yellow (e.g. a warning in the log)
Broken: The test couldn’t be completed due to an infrastructure error.
After filtering by status, you can further filter test results by tags that you previously applied to the test cases. It works the same as other parts of the Mesmer console that let you use tags as filters.
Test results can also be sorted using the “Sort by” dropdown:
Last Run: results from most recently run test cases come first
Status: results with “failed” and “needs review” status come first
Tags: results with tags come first
To view details about a particular test result, click its card in the Test Results screen. This will take you to a new screen where you can compare the baseline (known working) execution of the test case along with the actual results of the test.
In the title bar for the baseline and actual results, there is some information about the test run. You can click the title bar to expand or collapse the sequence of screens.
On each screen in the sequence, the action that Mesmer took is shown on the screen. These originate from an automatic crawl or scripted gestures taken while creating or editing the test case.
If an anomaly was detected during execution, the screen where the anomaly occurred will be tinted. Click the screen to see a detailed view of what Mesmer discovered, and how the screen specifically differs from the baseline.