Endtest

Endtest

›Advanced

Web Tests

  • How to create Web Tests
  • Finding elements in Web Applications
  • How to execute Web Tests
  • Assertions for Web Tests
  • IF Statements for Web Tests
  • Web Applications with restricted access
  • How to test in iframes
  • How to test in multiple tabs
  • How to test File Uploads
  • How to test File Downloads
  • How to test Emails
  • How to test PDF files
  • How to test Chrome Extensions
  • Dealing with reCAPTCHA
  • Dealing with Dynamic Locators
  • Dealing with Canvas Elements
  • Performing a Drag and Drop
  • Execute JavaScript
  • Testing WebRTC Applications
  • How to scroll in Web Tests
  • How to test Checkboxes
  • How to test Dropdowns
  • Dealing with Sessions
  • Web Crawler
  • Export Web Tests
  • Migrating from Selenium

Mobile Tests

  • How to create Mobile Tests
  • Finding elements in Mobile Applications
  • How to execute Mobile Tests
  • Assertions for Mobile Tests
  • IF Statements for Mobile Tests
  • How to scroll in Mobile Tests
  • Performing Complex Gestures

Advanced

  • Variables
  • Waits
  • Endtest API
  • Scheduler
  • Drive
  • Adding Collaborators
  • Computer Vision
  • Importing Test Cases
  • Using Loops
  • Data-driven Testing
  • Send API Requests
  • Read SMS
  • Execute SQL queries
  • Self-Healing Tests
  • Email Notifications
  • Slack Notifications
  • PagerDuty Notifications
  • Webhook Notifications
  • Automatic Backup
  • Advanced Settings
  • Multiple environments
  • How to stop a test
  • Utilities
  • Utilities API
  • Team
  • On-Premises

Integrations

  • Atlassian Jira
  • Slack
  • PagerDuty
  • Microsoft Teams
  • Discord
  • Mattermost
  • Jenkins
  • GitHub
  • Azure DevOps
  • GitLab
  • TeamCity
  • CircleCI
  • TravisCI
  • Bitbucket
  • Heroku
  • Bamboo Server
  • Test Case Management
  • SSO
  • BrowserStack
  • Sauce Labs

Computer Vision

Introduction

You can use the Computer Vision capabilities of our platform to ensure every part of the UI is tested.

If something changes on the screen, you will be alerted in the test results.

This method is also known as Visual Testing or Screenshot Comparison.

You can visually verify your entire page or only certain elements.

Guide

You can use one of these 3 options:

  1. Page Matches Screenshot
  2. Full Page Matches Screenshot
  3. Element Matches Screenshot

The difference between Page Matches Screenshot and Full Page Matches Screenshot is that the first option refers to the viewport, while the second option refers to entire DOM.

You can find those options in the Add Assertion and Start If Statement actions.

You must provide a Baseline Screenshot URL for those options.

How to obtain a Baseline Screenshot URL:

  1. Add a Take Screenshot,Snipping Tool or Generate Full Page Screenshot step in your test.
  2. Execute the test.
  3. Get the URL of the screenshot from the Results section.

If the screenshots have different sizes, the larger one will be automatically resized to match the smaller one.

The logs will display the baseline screenshot, the current screenshot and a third screenshot that highlights the visual differences:

endtest screenshot comparison computer vision

Each Computer Vision step will also have an Accept New Baseline button in the Results section. That action will update the Baseline Screenshot from that step with the Current Screenshot.

What is the Screenshot Tolerance?

The Screenshot Tolerance (%) from the Advanced Settings can be configured to manage the relationship between the percentage result and the assertion result.

For example, if you select 5%, your assertion will fail if the difference between the screenshots is more than 5%.

The Screenshot Tolerance (%) doesn't influence the precision of the screenshot comparison and the percentage result.

It only determines the percentage at which the assertion will be marked as Passed or Failed.

What is the Screenshot Fuzz?

The Screenshot Fuzz (%) from the Advanced Settings can be configured to set the precision of the screenshot comparison.

A smaller value will lead to a more precise screenshot comparison.

A higher value will lead to a less precise screenshot comparison.

An optimal value for the Screenshot Fuzz (%) is somewhere between 2% and 20%, but you can select values between 1% and 50%.

The Full Page Screenshot option is only available for Web Tests.

Since the webdrivers only allow you to take a screenshot of the visible viewport, the Full Page Screenshots are generated by taking multiple screenshots and stitching them together.

This may cause some elements with the CSS property position: fixed to be displayed multiple times.

If you're testing in multiple browsers and resolutions, we recommend having baseline screenshots for each combination.

You can manage those combinations by using If Statements and System Variables.

← Adding CollaboratorsImporting Test Cases →
  • Introduction
  • Guide
  • What is the Screenshot Tolerance?
  • What is the Screenshot Fuzz?
© Endtest Inc.