Should I scan every control on a page?

No. Select only the controls your tests use. Smaller, focused Modules are easier to understand and maintain.

When should I use Vision AI?

Use it when standard scanning cannot identify a control reliably, for example in some custom or graphical interfaces. Standard identification is preferable where it works.

Tosca Modules: Scanning Applications with XScan and Vision AI

Introduction

Modules are the foundation of every Tosca test. They hold the technical information Tosca uses to identify and operate the controls of the application under test. Instead of writing this by hand, you create Modules by scanning the application. This lesson covers the scanning workflow and Vision AI.

Prerequisites

The Tosca introduction lesson
An application you can open for scanning, such as a web application

Step-by-Step Guide

Step 1: Know what a Module is

A Module describes the controls of a screen or page in a way Tosca can use to find and operate them. Modules are the building blocks of TestCases: you reuse them to create TestSteps for any number of TestCases and test data.

Step 2: Open the scan

In Tosca Commander, you start a scan from the Modules section by choosing to scan an application, which opens Tosca XScan. In Tosca Cloud, the equivalent is creating a Module by scanning from the Build area. Menu paths vary by version, so follow the documentation for yours.

Step 3: Select the application and scan

Open the application to the screen you want, choose it in the scan window, and run the scan. XScan lists the controls it found. Select the ones your tests need rather than every control on the page.

Step 4: Review and save Modules

Check control names and types, remove what you do not need, and give Modules clear names that match the page or function. Save the Modules so they can be used to create TestSteps.

Step 5: Use Vision AI for hard-to-identify controls

Some controls cannot be recognized through standard technology. Tosca offers Vision AI scanning, which identifies controls visually, and lets you refine results, adjust control types, and create user-identified controls if needed. Check the Tricentis documentation for your version, including any special guidance when running with Distributed Execution.

FAQs

Should I scan every control on a page?: No. Select only the controls your tests use. Smaller, focused Modules are easier to understand and maintain.
When should I use Vision AI?: Use it when standard scanning cannot identify a control reliably, for example in some custom or graphical interfaces. Standard identification is preferable where it works.

Summary

Scan the application with XScan to create focused, well-named Modules, and use Vision AI when controls cannot be identified normally. Good Modules make every later TestCase simpler.