Reviewing Individual Test Results
Reviewing Individual Results
Upon clicking on a test result that you would like to view, you will be brought to a screen similar to the one below:
This is where you can get detailed information about the test. On the right hand side you can see the duration of each step. On the left hand side you can see whether each step passed or failed and what the step did. At the top of the test result you can see full status messages. This test result got a full pass!
Every step can be clicked on to display a side-by-side comparison of what was recorded for that step and the most recent result.
A rectangle will often appear indicating which element the step is interacting with. You can also click either "base" or "result" to display a full-sized version of the respective screenshots.
If you would like to edit the step, you can click "edit this step" at the top left of the window.
When a Step Fails
Now that we've seen what a passed test looks like, let's take a look at a failed test.
So let's take a closer look at step 6.
This brings us to a great point about building tests for the first time. Your tests may not automatically pass after the first recording, especially if you are using Javscript. There are many reasons errors can occur when building tests and it can take some editing before the test is ready to be used.
Full screenshots for failed steps
When a test fails, it can be useful to check the entire page to determine the cause, rather than the direct point of failure. For such cases, we have a feature that displays a full-sized version of each screenshot.
You can easily switch between
Fullpage screenshots by using the toggle in the top-left of each image. They can also be enlarged and scrolled through so you can check every detail.
*As of November 2022, this feature is only available in the PC Chrome environment.
Visual diff for test results
Do you ever want to see what parts of the screen have changed in appearance compared to the last time you tested? If you open the "Diff" tab for each step, the differences between the two screenshots will be highlighted!
The percentage difference is calculated based on changes in pixels and colors. We hope this will allow you to verify changes in appearance that were previously difficult to detect.
Browser log on Chrome environment
Have you ever wished you could see the log messages your web application outputs to the browser console - such as error messages that indicate API call failure - when you debug your tests? Here's a great feature that makes debugging easier than ever! When you have browser log messages available for a step in your test result, you can just click the number of messages displayed next to "Logs" at the bottom right of the step.
Once the log messages are displayed, it's also possible to filter them by log types (such as
ERROR) and keywords!
*Note: This feature is avaliable when you run your tests on Chrome, including mobile emulators
If you don't know why a test failed
If you are experiencing difficulties with a test and can't figure out why its not working the way it should, you can always click the "get support" button underneath the error message or click the "chat" widget at the bottom right hand side of the screen.