UFT One has covered aerospace Windchill testing for two decades. The question for 2026 is whether its object hierarchy approach and licensing cost still make sense when your primary automation surface is the Windchill Java PDM Link client and your budget is under pressure from OpenText’s post-acquisition pricing.

TL;DR

• UFT One uses hierarchical Java object recognition for PDM Link thick-client automation, reliable when the object tree is stable, but major PTC version upgrades that restructure the Java component hierarchy reset a meaningful portion of affected test scripts
• Sahi Pro uses proximity-based identification, elements are located by visible label and spatial relationship rather than object hierarchy, so PTC version upgrades do not reset scripts that identified elements by what they say and where they sit
• Both tools support full air-gapped on-premise deployment and satisfy ITAR data residency requirements without additional configuration
• UFT One licensing is confirmed by multiple enterprise user reviews as very expensive, with ROI timelines of two or more years, Sahi Pro licensing runs at a fraction of UFT One cost for equivalent Windchill PLM coverage
• Migration from UFT One to Sahi Pro for a Windchill suite is non-trivial but lower friction than a Tosca migration because Sahi Pro uses JavaScript and UFT One engineers can transfer scripting skills directly

The Aerospace Windchill Automation Problem in Plain Terms

Aerospace teams running Windchill have two distinct pressures on their automation programme that other industries do not share.

The first is compliance. AS9100D requires structured execution records, and ITAR requires that every byte of test execution data, logs, screenshots, reports, stays within approved networks. These requirements were covered in the Windchill aerospace listicle earlier in this series. For this comparison, both UFT One and Sahi Pro satisfy them, so compliance is not the differentiator here.

The second is upgrade cost. Aerospace Windchill deployments move slowly through PTC releases because every version upgrade triggers a revalidation cycle. When those upgrades do happen, a team running XPath-dependent or Java object hierarchy-dependent automation faces a maintenance bill proportional to how much PTC changed the interface. That bill is predictable, it recurs, and it compounds with every upgrade cycle.

The identification approach a tool uses determines what that bill looks like. Object hierarchy recognition ties element identity to the object’s position in the Java component tree. Proximity-based identification ties element identity to what the element visibly says and where it visibly sits relative to other elements. When PTC restructures the PDM Link Java client, the visible labels on BOM panels, change order fields, and part classification attributes mostly stay the same. The component tree does not.

That architectural difference is the primary decision driver for teams choosing between UFT One and Sahi Pro today.

What UFT One Does Well on Windchill Aerospace

UFT One has genuine strengths that justify its long tenure in aerospace automation programmes. Start here before considering a switch.

UFT One’s Java Add-in has 20 years of enterprise Java application testing behind it. The object recognition for Java Swing and AWT controls is deep and well-documented. For Windchill PDM Link components where the Java component tree is stable across releases, standard dialog boxes, navigation panels, fixed-structure forms, UFT One identifies and interacts with elements reliably.

UFT One’s compliance documentation capabilities are mature. Two decades of deployment in regulated aerospace and defence programmes means the tool has been through many audits. AS9100D evidence package development using UFT One output is a well-understood process in most aerospace QA teams.

UFT One supports full on-premise deployment with no external data routing. ITAR compliance is achievable without additional configuration.

The support organization is enterprise-grade. For programmes where a test suite failure during a launch programme needs a same-day vendor response, UFT One’s OpenText support model with defined SLAs is a meaningful differentiator over tools with community-based or lower-tier support.

Where UFT One Creates Friction for Aerospace Windchill Teams

The friction accumulates in three places.

Post-upgrade maintenance. UFT One’s Java object recognition identifies elements by their position in the Java accessibility tree, component type, parent-child relationships, property values like name and index. When a major PTC Windchill release restructures the Java client interface, renaming components, changing panel layouts, updating the object hierarchy, tests that relied on the previous tree structure fail. For aerospace teams running 200 or more Windchill test cases, post-upgrade maintenance can run to weeks of engineering time per upgrade cycle.

Canvas attribute grids. Windchill’s Java PDM Link panels render classification attribute grids as canvas elements, painted pixel regions with no accessible Java accessibility tree. UFT One’s Java Add-in relies on the accessibility layer. When that layer returns nothing, UFT One cannot interact with the element. Canvas-rendered attribute grids in Windchill’s advanced classification panels are outside UFT One’s standard scope.

Licensing cost. Multiple independent user reviews on TrustRadius and G2 describe UFT One as “very expensive,” with common observations that ROI takes two or more years to materialize. Since OpenText acquired Micro Focus, licensing costs have increased further. For aerospace programmes evaluating tools on a cost-competitive basis, this is often the first constraint teams hit.

How Sahi Pro Handles the Same Windchill Scenarios

Sahi Pro’s answer to the Windchill aerospace context runs across three layers.

The core product handles Windchill’s browser portal through proximity-based element identification, tests locate elements by visible label and spatial context, surviving Active Workspace updates without locator rewrites.

The Desktop add-on covers Windchill PDM Link Java thick-client natively through Java Swing, AWT, and SWT access. BOM management panels, engineering change workflows, and configuration management interfaces in PDM Link are reachable in the same test framework as the browser layer. Proximity-based identification means a test that navigates to a BOM panel and validates part attributes continues to work after a PTC upgrade that changes the component tree, because the test found the panel by its visible label, not its component hierarchy position.

The AI Assist OCR add-on reads text directly from canvas-rendered regions. Classification attribute grids in PDM Link that paint values to the screen as pixel regions, outside the Java accessibility layer, are accessible through OCR-based identification. When PTC changes the layout of an attribute grid, OCR continues finding the right field by reading its visible label.

ITAR compliance is standard. On-premise deployment with no external data routing is the default configuration, not a special mode.

AS9100D execution record output produces timestamped, step-level records from the standard report format without custom post-processing.

Side-by-Side: The Factors That Drive the Decision

The Other Three Tools in Brief

Tricentis Tosca: Strongest governance model for large programmes with centralized test management. Java PDM Link coverage exists through TCD models. Canvas attribute grids require additional modules. Highest cost of the five tools. Correct choice for programmes where centralized compliance governance outweighs cost.

Ranorex: Handles WinForms, WPF, and standard Java Windows desktop automation well. GDI/GDI+ plugins reach challenging UI elements. Canvas-rendered Windchill attribute grids have documented AWT accessibility limitations. Appropriate for aerospace teams whose Windchill automation scope does not include canvas-rendered classification panels.

Selenium: Covers Windchill’s browser portal. ITAR-compatible in an on-premise configuration with no cloud tooling added. Java PDM Link and canvas attribute grids are outside scope. Correct baseline for programmes where browser-portal automation is the entire test scope.

What a Migration From UFT One to Sahi Pro Actually Involves

For teams seriously evaluating this switch, scope the effort honestly before committing.

What transfers: Test logic, test data, and suite structure translate directly. VBScript to JavaScript is not a trivial translation, but engineers who know VBScript learn JavaScript faster than engineers who know neither. Business logic, what to test, in what sequence, with what data, transfers completely.

What needs to be rebuilt: Element identification. UFT One object repository files do not translate to Sahi Pro’s identification approach. Every element reference needs to be re-established in Sahi Pro. For a 200-script Windchill suite, budget eight to twelve weeks for an experienced automation engineer to complete the rebuild, plus validation time.

What gets better: Post-upgrade stability. Teams that have migrated from object-recognition tools to proximity-based tools consistently report that the first PTC upgrade after migration reveals the maintenance cost difference. Scripts that required two weeks of repair under UFT One require one afternoon under Sahi Pro.

Request a migration assessment from the Sahi Pro team with your specific script count, PLM version, and scope before finalizing the timeline.

Sources

• OpenText UFT One reviews and pricing commentary: TrustRadius, trustradius.com/products/opentext-uft-one
• OpenText UFT One on G2, g2.com/products/opentext-functional-testing
• ITAR 22 CFR Parts 120-130: International Traffic in Arms Regulations, ecfr.gov
• AS9100D clause 8.5.6: Quality Management Systems for Aviation, Space, and Defense, sae.org
• Sahi Pro: 7 Best PLM Test Automation Tools for Aerospace and Defence Compliance in 2026, sahipro.com/blog-plm-test-automation-tools-aerospace-defence-compliance-2026/
• Sahi Pro: Self Healing Test Automation for Teamcenter: Proximity-Based Element ID, sahipro.com/self-healing-test-automation-teamcenter/