The test editor

Use the Test editor to navigate through the steps in a test result and investigate differences between checkpoint and baseline images in a step. When reviewing a step, you can resolve the image differences by accepting or rejecting the differences. If the action you perform in one step is a maintenance action, then the Test Manager prompts you to apply the action to all other steps that fall within the scope that was set for Automated test maintenance.

The Step editor and Test editor both allow you to review steps, resolve step differences, and accept or reject changes, with the following differences:

  1. The Test editor opens in the entire Test Manager window, the Step editor opens in a smaller panel that overlays the current window.

  2. The Test editor only works with steps in a test, whereas the Step editor handles steps in a test or batch.

  3. The Test editor initially loads images in a larger size.

  4. Navigation between steps differs between the two editors.

Accessing the Test editor

You can access the Test editor from either the Batch details view or the Batch steps view while viewing step thumbnails.

To access the Test editor:

  1. In the Test results page, select a test and click or to open the test in the Batch details view or the Batch steps view.

  2. Below a thumbnail, click > Open in test editor.

Changing the view

View baseline and checkpoint images

The Test editor displays either the checkpoint image of the step, the baseline image, or both images side by side. Click anywhere on the image control , or press the T key to toggle between the baseline and checkpoint images. Click the dropdown menu to select a specific view.

Zoom in and out of the step images

The Zoom controls allow you to adjust the image size in the browser, letting you either view the entire image or focus on details in one area.

For more information see Test editor zoom controls.

Select visible layers

Use the select visible layer control to select what information is overlaid on the step image. For more information see Test editor select visible layer.

Hide displacement diffs

The Hide displacement diffs tool in the Step editor and Test editor hides differences caused by content that has moved on the page. This is useful, for example, when content is added or removed, causing other elements on the page to shift and generating extra differences.

When a large area of the page is impacted by such a change, the page can fill with pink mismatched areas, making it difficult to spot actual content changes. By using this tool, you can hide content that has only moved and focus on mismatches caused by real content changes.

For more information see Hide displacement diffs tool.

View Root Cause Analysis (RCA) data

Click the button or press the I key to open the Root Cause Analysis (RCA) panel.

The editor displays RCA information when you click a pink area that flags a visual difference in the checkpoint or baseline image panels. The editor compares the DOM and CSS information stored with the images, displaying significant differences for any DOM elements that may impact the diff. RCA also lets you manually select the elements whose DOM and CSS information will be compared.

For more information see Using the Root cause analysis feature.

View the test details

Open the Test details dialog box by clicking the drop-down menu in the View toolbar and then clicking Test details.

The Test details dialog box displays reference information on the Test and the Baseline to which the test belongs. Some of the information provided is general information, and other details can be used for troubleshooting.

For more information see Viewing test details.

Show the baseline and baseline history pages

You can open the Show baseline and Show baseline history pages from the menu.

Show baseline – Opens the Branch baselines page, listing all the baselines of the test.

Show baseline history – Opens the Baseline history page, listing all past revisions made to the test baseline.

Preview the step images using match level options

Use the Preview match level options to preview how the checkpoint and baseline images would be displayed at different match levels. The following match levels are available:

  1. Exact

  2. Strict

  3. Ignore colors

  4. Layout

For more information on Match levels, see Match levels.

To display the baseline and checkpoint images using any of the match levels, click , hover over Preview match level, and select a match level.

You can create a match level region that will be used in a future test by marking the area with a match level region as described in Defining Regions. You can also define a match level for the entire test using the SDK method configuration.setMatchLevel or for an region or element in a specific checkpoint using the method setMatchLevel.

Undo changes in the test

Use the Undo changes in test option to undo changes that haven't been saved to the test baseline. This reverts the test status to the state after the most recent save.

Highlight differences between the Step baseline and checkpoint images

Use the Diff Navigator to highlight diffs that appear in the step baseline and checkpoint images.

Click to highlight differences in the images. Circles will flash wherever differences are found. If a difference is outside the current field of view, a circle flashes, and a blurred pink strip appears on the edge of the view to indicate the direction you need to scroll to see the difference.

Click or press the . key to move to the next difference. Click or press the , key to view the previous difference. After you view the last difference, the zoom level returns to its previous setting.

Add issue and remark regions to the step images

You can annotate one or more remark or issue regions on the baseline or checkpoint image of a step. The region marks a specific area and includes a description, discussion thread, and other features. For further information, see Adding issue and remark regions

Defining Regions

Different parts of the screen can have specific requirements. For example, you might want to ignore the space where an ad banner is displayed on all screens that include the banner. To accomplish this, you can create a region and assign it a specific match level.

You can define a region based on one of the following methods:

  • Element-based – (recommended) A dynamic region based on a web element, such as a frame, image, text box, or video. When you click on an object on the screen, Eyes automatically identifies the screen element. This method is recommended because Eyes can recognize the element even if its exact location on the screen changes.

  • Drawn – A region based on coordinates on the screen. This is useful if you want to define a fixed area that is not linked to a single element or create a region around multiple elements.

For more information, see Defining Regions.

Set the Automated Maintenance scope

Setting the Automated test maintenance scope lets you control the extent that Automated maintenance operates over the steps in a batch. You can set the scope to default, batch, explicitly selected tests or steps in a batch, or the current step only.

Set the scope by selecting an option from the Auto Maintenance menu in the Step editor tool bar.

For more information see Setting the automated test maintenance scope.

Accept or reject changes made to the steps

Resolve differences in a step by accepting or rejecting the differences.

Click to accept the differences and checkpoint image of a test's step, and then advance to the next step that has differences.

Click to reject the differences and keep the baseline image of a test's step, and then advance to the next step that has differences.

Note that Accepting and Rejecting differences are Automated test maintenance operations and the range over which the selected function operates is dependent on the scope you set for Automated Maintenance.

For more information see Accepting and rejecting steps.