After you run Eyes visual UI tests, you use the test results page to see the outcome of the test runs, and if necessary, to update the test baselines.
Using the controls and tools on this page you can you can analyze the results of the test run by filtering, sorting and grouping the information in various ways. You can look at, and compare the baseline and checkpoint images. You can accept a checkpoint image so that it will become the new baseline image. Alternatively, you can reject a step, indicating that the step failed, and you can assign the test to a team member for further action.
You open this page using the page navigatorThe Page navigator is a control at the top of the Test manager window, that is used to switch between the main pages of the Test manager. It also displays the name of the current page. Test result menu entry.
The test results page is divided vertically into two panels. On the left, you can see the batch list - a list of all the batchesTwo or more tests can be grouped together into a "batch" using the SDK set batch method/property. In the Eyes Test Manager Test result page, you can see a list of all the batches that have run. run by your team. When you click on any entry in the batch list, it becomes the current batch, and the main panel shows information on the test results of that batch. The information you can see depends on the view you select using the view selector - each view focuses on a different aspect of the test results (Batch level, tests, steps and issues & results). See The test results views below for more about what you can see and do in each view.
The batches in the list are ordered time-wise, with the most recently run test first. Since the batch list can be very long, it is updated only when you scroll further down the list.
Each entry in the batch list displays the batch name, the date and time the batch started running and a batch status (Running, Passed, Failed - see Understanding the batch status). There is also an indication if you have started resolving the tests but have not yet saved the results and a checkbox that is used to select the batch for deletion.
When you click a batch in the list, it becomes the current batch and information about that batch will be displayed in the main panel.
At the top of the main panel there is a panel that provides information about the currently selected batch:
The information displayed includes the name of the current batch, when the first test in the batch started, how long it took to run and how many tests there are in the batch. This is followed by a breakdown of the numbers of tests in different states : unresolved, aborted, failed, new, running, passed, or have issues. Only values that are non-zero are displayed. The current batch status (Passed, Failed and so on) and save state are also displayed here - See Test and batch status more details.
You can rename the current batch by hovering over its name, clicking on it and typing in a new name - see How to rename a batch for more details.
The save changes to baseline button will "pulse" when you have made changes and have not yet saved them to the baseline.
Click on the button to save all the tests. If you don't want to update the baselines of all the tests (since this will immediately impact tests when they next run), then in test details view, select Save selected test to baseline in the sub-menu opened when you hover over this button.
Since tests can be running in the background, the information on this page may not be up-to-date. Both the batch toolbar and the test toolbar have a button. If these indicators rotate, then this means that more information is available on the server. Click on the button and the panel associated with that button will be updated.
The current batch toolbar contains buttons that allow you to select the current view:
The other buttons in the toolbar view toolbar always contains the same buttons, but some of the operations are only enabled in some of the views, others behave slightly differently in each view. The buttons are described in the view documentation.
This view provides you with a high level view of the results of the test runs, and the progress in processing these results, This view displays graphical summaries of key test attributes and states. For example, you can see the percentage of tests that have mismatches, the percentage of the steps that have been resolved, what browsers and operating systems the tests ran on and more.
In the test detail and step details views, you can see thumbnail images steps. In the test details view, these are initially hidden, and you can see all the steps of any test by clicking on the test. In the step details view, you can filter and group the steps by various criteria.
You can open the test and step editors from any of the views that display a step thumbnail. Clicking on the thumbnail will open up the test editor. You can open the step editor using the step thumbnail menu. The main difference between the test editor and the step editor is that the test editor allows you to navigate through all the steps in a test, whereas the step editor allows you to step through all the steps in a batch, taking into account any filtering and grouping that you have applied to the test results page.