3.4.  Verifications View

Table of Contents

3.4.1. Messages with Screenshots or Verification Points

The verifications view gives you a detailed view of the results of a test run. It shows the passed and failed verifications, as well as log messages, error messages, stack traces and screenshots taken during a test run.

The results are structured by Reports, which you can select in the Batch Reports menu on the left side. The result table can be filtered based by Fails, Warnings or Passes.

This view can be reached from the Dashboard (Section 3.1) and the Explore View (Section 3.2) by clicking on the passed () or failed () icons.

Verifications View

3.4.1.  Messages with Screenshots or Verification Points

Messages with a screenshot, failed visual and table verifications have a camera icon for a link to the image file or visual or table result file.

3.4.1.1.  Screenshot Verification Point

Clicking the camera icon for a screenshot comparison failure opens a popup showing the image. With a right mouse click on the camera, the image can be saved to disk.

Screenshot Verification Dialog

The dialog can be closed by either clicking the X located top/right or simply by reloading the page.

By clicking in the bottom bar Compare with VP file the screenshot verification point (screenshot VP) file from the test suite can be uploaded, and the two images can be compared. The one from the tests results, the actual screenshot and the one from the uploaded VP, the expected image. Close the uploaded VP with a X-button click.

Bottom bar after VP upload

The Patched VP file creates a screenshot verification point file by replacing the image in the uploaded VP with the actual one and asks for a download location. The downloaded file can replace the matching VP file used in the Squish test suite.

3.4.1.2.  Table Verification Point

Table Verification

Clicking the camera icon for a table comparison failure, a simple row by row difference is shown. Green rows replaces the pink expected rows of the table verification point.

3.4.1.3.  Visual Verification Point

With a visual verification point (VVP) failure during a Squish test run, a dump of the application actual user interface (UI) is saved in the results. As mentioned, the camera icon represents the link to the failed VVP results. With a right mouse click, that result file can be saved and then later viewed with the Squish utilities uibrowser or visualvpeditor. But also this dump can be made visible in Squish Test Center, by clicking on the camera icon. A uibrowser like view will be shown as below.

Actual VVP View

The left side is for the application objects, shown hierarchical. The center is for the image and highlights the current application object selected. The right side shows object properties when an application object is selected.

By clicking Compare with VP file the visual verification point file can be uploaded, and Squish Test Center performs a comparison between the uploaded expected UI and the one from the results, the actual UI.

Expected VVP Compared with Actual

The letter icons in the application objects tree represents Geometry, Hierarchical, Property (or properties), Screenshot or Type error. The geometry and/or property errors are also shown on the right as red marked values. There could also be a N/A, not available, icon. Which means that a similar object isn't found in the actual UI.

On the bottom, the view can switch between the original Actual visual to the Expected uploaded verification point file. Close the expected VVP upload with a X-button click. The left and right Browse Errors buttons move the selected application object to the previous or next object with error.

The Patched VP file creates a visual verification point file out of the actual result file by copying all checks over from the expected VVP file and asks for a download location. The downloaded file can replace the matching VVP file used in the Squish test suite (in case the original VVP file is out of date).

Finally the VVP view can be closed by either clicking the X located top/right or simply by reloading the page.