HPE UFT and QTP Testing

Many organizations are questioning whether HPE UFT/QTP remains the best solution for their testing needs as they face expectations for 2-week Agile sprints, CI integration for DevOps, and the highly-orchestrated testing required for APIs and microservices. However, they’re reluctant to replace HPE because of all the time and effort they already invested in building massive HPE regression test suites.

At Tricentis, we’re committed to helping enterprises leverage and extend legacy HPE tests for tackling today’s testing challenges. We can automatically migrate existing HPE tests to Tricentis Tosca, the functional testing platform that’s driving the market forward.

Why Replace HPE UFT/QTP Tests?

HPE UFT is the latest generation of the functional testing tool that was born in May 1998 as Mercury Astra QuickTest. This tool was developed by Mercury, sold to HP in 2006 (as QTP), rebranded as UFT (Unified Functional Testing) in 2012, then spun off to Micro Focus in 2016.
Across the various ownership and name changes, one thing remained constant: reports of low overall test automation rates. This is commonly blamed on slow regression test execution, brittle tests, high false positives, and—most frequently—burdensome test maintenance.
With the HPE-Micro Focus acquisition occurring when many customers were already unsure if the HPE platform was fit for modern application architectures and processes, many HPE customers have started exploring alternative testing solutions.

HP Testing Alternatives

Reduce Tests & Time
Increased Risk Coverage

A leading European insurance company accumulated 15,000 HPE UFT regression tests that took 10 weeks to execute (and achieved unknown risk coverage). By migrating to Tricentis Tosca, they cut their test suite size by approximately 55%, reduced test execution time from 10 weeks to 8 hours, and increased risk coverage to 82%.

Get details about their HPE migration process

HPE UFT/QTP Test Import Details

The fully-customizable HPE test migration process converts technical information, test case logic, and test data:

Test data

Existing test data is captured and imported into a comprehensive repository of stateful test data objects. This data can then be used across all automated test cases and service virtualization assets. It is easily readable and manipulated via a business-readable UI. Moreover, it can be rapidly extended with synthetic test data generation—increasing coverage to help expose defects.

Technical information

Details about the system under test are migrated to a business-readable representation of core elements. Multiple types of tests artifacts can then be rapidly defined based on this model. Since each unique technical element is represented by a single model element, test maintenance is simple and centralized.

Test case logic

Test case logic is imported into Tricentis Tosca and translated into our model-based test framework. Unlike scripts, the resulting tests are simple to understand and extend as the associated application functionality evolves.