tldr: The Tricentis Automation Extension for Chrome lets you scan web applications directly in Chrome to create Tosca modules. It identifies UI elements on a page and maps them to module attributes via Tosca's XScan feature. Available on the Chrome Web Store.


What the Tosca Chrome extension does

The extension is officially called Tricentis Automation Extension. Tosca uses "scanning" to identify UI elements in your application and create modules. The Chrome extension works with Tosca's XScan feature to scan web applications running in Chrome.

When you activate the extension, Tosca overlays your web page with element highlighting. Click on buttons, input fields, dropdowns, or any UI element, and Tosca captures its properties: element type, attributes, position, text content. These captured elements become module attributes in Tosca Commander.

Without the extension, you can't create XBrowser modules for web applications in Chrome. It's a required component for web testing.


How to install and use it

Installation:

  1. The extension is available on the Chrome Web Store (search "Tricentis Automation Extension")
  2. Install it directly from the store, or from Tosca Commander for offline/air-gapped environments
  3. A Microsoft Edge version is also available on the Edge Add-ons store
  4. Chrome will prompt you to confirm the extension installation
  5. Enable the extension in Chrome's extension manager

Using XScan in Chrome:

  1. Open your web application in Chrome
  2. In Tosca Commander, right-click your module folder and select "Scan > Application"
  3. Select "Web Browser" as the scan type
  4. The Chrome extension activates, highlighting scannable elements
  5. Click elements to add them to your module
  6. Fine-tune element properties in Tosca Commander
  7. Save the module

Re-scanning after UI changes:

When your application's UI changes, re-scan to update module attributes. Open the existing module, trigger a rescan, and Tosca identifies changed or new elements. This is how you maintain modules over time.


What elements it captures

The extension captures standard web element properties:

PropertyDescription
Element typeButton, input, select, div, span, etc.
HTML attributesid, class, name, data-testid, aria-label
Text contentVisible text within the element
PositionXPath and CSS selector paths
Parent hierarchyDOM tree structure for context

Tosca uses these properties to build locator strategies. During test execution, Tosca tries multiple properties to find each element, providing some resilience when individual attributes change.

For more advanced element recognition, Tosca's Vision AI (separate license) adds image-based identification on top of the DOM-based scanning.


Known limitations

Chrome and Edge only. The Tricentis Automation Extension is available for Chrome and Edge. Scanning in Firefox or Safari requires different scan modes or may have limited support. Check your Tosca version for current browser scanning capabilities.

Extension compatibility. Chrome updates can occasionally break the extension. Tricentis releases compatibility patches, but there can be a lag between Chrome updates and Tosca extension updates. Pin your Chrome version in enterprise environments to avoid surprises.

Dynamic content. Single-page applications (SPAs) with heavy JavaScript rendering can be tricky. Elements that load asynchronously may not appear during the initial scan. You may need to interact with the page to trigger dynamic content before scanning.

Shadow DOM. Web components using Shadow DOM can be partially or fully opaque to the scanner. This is a known limitation. Workarounds include using Vision AI or custom scanning configurations.

iFrames. Tosca handles iFrames but requires frame switching in your modules. The scanner can identify iframe boundaries, but you need to configure frame handling explicitly.


Tosca scanning vs. modern approaches

Tosca's scan-and-build-modules workflow is methodical. It works. But it's a 2015-era approach to a 2026 problem.

Modern AI testing platforms skip the scanning step entirely. Instead of capturing DOM elements and building modules, you describe what you want to test in plain English. The AI figures out how to interact with your application at runtime.

AspectTosca XScan + Chrome extensionBug0
ApproachScan elements, build modules manuallyDescribe tests in plain English
SetupInstall extension, configure Tosca, scan pagesType a test description
MaintenanceRe-scan when UI changes, update modulesAI self-heals automatically
Learning curveWeeks to master module designMinutes to first test
Browser requirementChrome extension requiredNo extension needed

For teams already using Tosca, the Chrome extension is a necessary tool. For teams evaluating options, Bug0 offers a fundamentally simpler workflow: describe what you want to test, and AI handles the rest.


FAQs

Where do I download the Tricentis Tosca Chrome extension?

The extension (called "Tricentis Automation Extension") is available on the Chrome Web Store. Search for it directly in Chrome, or install it from Tosca Commander for offline environments. An Edge version is also available on the Microsoft Edge Add-ons store.

Does the Tosca Chrome extension work with other browsers?

The Tricentis Automation Extension is available for Chrome and Microsoft Edge. Tosca offers different scan modes for other browsers, but Chrome and Edge are the primary scanning targets. Check your Tosca version's documentation for current multi-browser scanning support.

Why does the Tosca Chrome extension stop working after a Chrome update?

Chrome updates can break extension compatibility. Tricentis releases patches to restore compatibility, but there may be a delay. Enterprise teams often pin Chrome to a specific version to prevent unexpected breakage.

Is the Tosca Chrome extension required for web testing?

For creating web testing modules in Tosca, yes. The extension enables XScan to capture web elements. Without it, you'd need to manually define module attributes, which is impractical for modern web applications.