Mask UI Check

Quite often a test might include dynamic data on screen that is expected to change between test runs and should not cause the test to fail. By default, when you run a test we can't recognise that this is dynamic data and might:

Example:

To avoid this you can 'mask' certain regions/areas on a UI check screenshot. This causes those regions to be ignored when the UI Check is executed during a test run.

To mask regions on a UI check:

Note: If you have masked regions set up for the prior step then the 'Mask Content' pop-up should show an additional 'Copy From Previous Step' button. You can click this to copy across the masked regions from the previous step. This is useful if you have multiple sequential steps on the same screen that all require UI Checks, as it saves you having to keep manually adding the same regions to each screenshot.

Note: When you are viewing a test case run/execution, and you are comparing the expected vs actual UI for your UI Checks, you can toggle the visibility of the masked regions to help you more clearly understand why a test step might have failed and what was considered during the test run.

The video at the top of this guide provides more explanation on the above and an example. We strongly recommend that you watch this video before using this feature.