No. Selenium automates web browsers only; desktop and CAD applications such as CATIA fall outside its scope and need separate tools bolted on. In this PLM project the team’s Selenium scripts reached only the web layer, leaving CATIA and SAP manual. Sahi Pro automated all three in one engine, using Visual Assist (OCR and image recognition) to drive CATIA, which exposes no standard automation interface.

CAD applications like CATIA rarely expose stable UI objects, so element-based tools cannot reliably see them. The dependable approach is screen-level automation that recognizes controls visually. Sahi Pro’s Visual Assist uses OCR and image recognition to automate CATIA the way a user works with it, which is why a live CATIA demo succeeded where Selenium and Tricentis Tosca could not.

A. Most tools cover one layer and force teams to stitch several together. Sahi Pro runs web, desktop (CATIA), and SAP in one continuous flow on a single engine. In this project that consolidation moved automation coverage from web-only to web + desktop + SAP, a 4x increase, with no separate toolchains to maintain.

Most maintenance comes from scripts breaking when the UI changes, usually due to fragile element identification. Sahi Pro’s robust element identification keeps scripts stable across UI updates. In this project that cut script maintenance effort by 40% and let the regression suite run as one continuous flow instead of disconnected chunks.

No. Sahi Pro uses low-code authoring, so the whole QA team can automate rather than only developers. In this project the team automating the full PLM stack went from 7 engineers hand-coding Selenium to 2 running a single flow.

Tricentis Tosca was evaluated for this PLM environment but could not automate the end-to-end flow across web, CATIA desktop, and SAP. Sahi Pro covered all three in one engine and proved CATIA automation in a live demo. For teams needing genuine multi-layer PLM coverage rather than web or SAP alone, that single-engine reach is the deciding factor.