Skip to main content

Tricentis Tosca

Tricentis Tosca is a cutting-edge software testing tool that uses artificial intelligence and analytics to optimize testing processes. It simplifies testing workflows with its model-based approach for both automated and manual testing across multiple platforms and technologies. This enables faster, more reliable testing, making it a valuable tool for DevOps and Agile environments.

The Applitools integration adds AI-powered visual validation to your Tosca tests through a set of Special Execution Task modules that drive the Applitools Eyes browser extension.

Requirements​

  • Tricentis Tosca. Use the integration build that matches your Tosca installation.
  • .NET 8 runtime. The integration's Special Execution Task assembly targets .NET 8.
  • A Chromium-based browser (such as Google Chrome) launched with remote debugging enabled. The integration attaches to the browser over the Chrome DevTools Protocol on the configured debugging port (see ChromeDebugPort and Debug Port).
  • The Applitools Eyes browser extension, installed in that browser. It performs the visual capture and comparison.

Downloads​

Eyes Browser Extension

  • To download the latest version of the Eyes Browser Extension, click here.
  • To download a specific version, use this URL template with your desired version number specified:
https://sdksstorage.blob.core.windows.net/eyes-browser-extension/<version number, e.g. 0.5.2>/eyes-browser-extension.zip

Required Tosca Files

Integrating Tosca With Applitools​

  1. Download the integration zip file and unzip on your local machine. Important: make sure you provide permission on the dll's to execute them. Right click and on the dll's and choose to allow execution. This article explains the unblocking process.

  2. Open the Tosca commander and load your project.

  3. Open Project Settings and add the directory to your TBox Extensions as shown below. Be careful not to create duplicate directory entries under "Extension Folders" and note that you do not have to use "Applitools" as the value name. The Value name is provided as a place for you to put a useful name and is not integration specific.

    Extension

  4. Import the provided TSU subset into you project. The modules should look like this.

    Modules

  5. The the imported subset contains a sample test that looks like this. Make sure you change the test configuration parameters to match you Applitools API key and Applitools server name (https://companynamehereeyes.applitools.com for example, or if you use the public cloud use https://eyes.applitools.com).

    Config

How the integration works​

The integration ships as a set of Tosca Special Execution Task modules. Each module drives the Applitools Eyes browser extension, which performs the visual comparison and uploads results to the Applitools server. A test typically uses these modules in order:

ModulePurpose
EyesActivateSWAttaches to the browser's remote-debugging port and wakes the Applitools Eyes browser extension's service worker so it is ready to receive commands. Run this before opening Eyes.
EyesOpenStarts an Applitools test. Reads the test identity, viewport, batching, browsers/devices, and accessibility settings.
EyesCheckCaptures a checkpoint (full window or a region) and compares it against the baseline using the configured match level.
EyesCloseCloses the Eyes test and reports the result status (for example, All Tests Passed or Some Tests are Unresolved).

Usage notes​

  • Keep the browser open for the entire run. The integration drives a live browser through the Eyes browser extension; closing the browser mid-test breaks the connection.
  • Close the browser or WebDriver only after EyesClose. Close the Eyes connection with EyesClose before the automation closes the browser or WebDriver session.
  • Add an EyesCheck for each validation. A test can contain any number of EyesCheck steps; each one corresponds to a single page or component validation.

Configuration reference​

For the full list of options, see the API reference: