With continued uncertainty surrounding the future of HP testing solutions, we’ve experienced an increase in questions about our HP test migration tool.

The Tricentis migrator imports HP UFT/QC tests into Tricentis Tosca to accelerate the upgrade to model-based test automation. The goal is to help you transition as rapidly and effortlessly as possible—so you can start taking advantage of additional testing best practices such as risk-based test case design, risk coverage optimization, synthetic test data generation, and more.

Here’s a recap of some the most frequently asked questions we get about migrating from HP UFT testing…

Where do I get the HP test framework migrator? Is special licensing required?

The Tricentis Tosca Migrator and sample HP migration projects are available on the Tricentis GitHub. No additional Tricentis license is needed. It is free (under the MIT License), available for use with any Tricentis license that includes test automation.

What types of HP tests can be migrated?

Tests from HP UFT or HP QC can be migrated. You can also migrate tests from Selenium—but we’ll cover that in another blog.

What test information is migrated?

We migrate technical information, test case logic, and test data from HP UFT and QC.

Technical information

Details about the system under test—across the UI and other (API, database, etc.,) layers—are migrated to a business-readable representation of core elements. Multiple types of tests 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: update the model once and changes are automatically propagated across all associated test artifacts.

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.

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. It is easily readable and manipulated via a business-readable UI. Moreover, it can be rapidly extended with synthetic test generation—increasing coverage to help expose defects

Can the HP test framework migrator be customized?

Yes, you can customize the migration logic to suit your organization’s specific needs and preferences. Through GitHub, you can also benefit from other users’ extensions. If you want to streamline the adoption or customization process, Tricentis Services is always available to assist.

Where can I learn more?

If you’re already a Tricentis customer, you might want to watch the on-demand webinar outlining the HP UFT migration process to see the migration process in action.

If you’re still wondering if HP migration is the right path for your organization, take a look at our HP UFT Alternatives page to learn more about how the tools compare.

In either case, you might also want to read our blog on Migrating HPE UFT Tests: Reduce Maintenance, Increase Risk Coverage & Accelerate Testing for a glimpse at one customer’s migration path.

Tricentis acquired Flood IO load testing - learn more