To see a list of test cases accepted into your app’s project, open the “Test Cases” dropdown from the top of the screen and choose “Manage Tests”.
This will take you to a screen with the entire set of test cases available, and a status summary at the top.
Each test case has a title. You should assign meaningful titles that distinguish what exactly is being tested, compared to other tests in the project. The test case allows collaborators to make comments and assign the test case to others.
To run all the tests, click the “re-run tests” button on the right of the console.
You will then see a menu of devices to run the tests on. Select the device a click “Run”. The tests will start momentarily. When they start running, the test cases screen will indicate which test is currently being executed using an animated circle. Other test results will be marked to match the color coded status counts at the top (Passed, Failed, Broken, Needs Review).
Clicking a running test will show its progress. Clicking a test with a non-passed status will allow you to examine, in detail, what problems Mesmer found with the test case.
To narrow down the set of test cases to something more easily actionable, click any one of the status types with a count above the test results. For example, to see all broken tests, click the black “broken” status count. You can further filter the results by more granular status using the grey descriptors just below the status counts. Each granular descriptor also has a sub-count in parenthesis.
You can use tags to help categorize and group test cases. Read more about test case tags.
For any test case that did not pass in its most recent execution, you can examine the anomalies discovered by Mesmer by clicking the test case. It will show a summary of which screens had differences compared to the “baseline”, which is the most recent successful run.
Click the expand button to the right of the baseline screen to see all of the screens of the most recent test result. Screens with anomalies will appear tinted to indicate where an anomaly was found. Click a screen to view a comparison between the baseline and test result.
When hovering the mouse over a test case, its action buttons are revealed in its row. Or, when the browser window is narrow, a popup with the actions can be seen by clicking the overflow menu button.
This action clones the test case and its configuration into a new test case of your naming. You can then edit the new test case to alter its behavior.
This action downloads a zip file containing the test configuration as a JSON file, including full-resolution screenshots.
This action deletes the test case. Deleted test cases can’t be recovered.
This action shows a popup form where you can enter specific configurations for the test case, to be used at the time it’s running. You can add values for:
Other custom data
The documentation for adding test data will be improved in the near future.
This action navigates to a new screen where you can modify a test case by setting up preconditions and assertions for each screen, or deleting steps from the test.
The documentation for editing test cases will be improved in the near future.
Click the user avatar or name to reassign the test case to another user who has been invited to collaborate.