HPE Testing

Migrating HPE UFT Tests: Reduce Maintenance, Increase Risk Coverage & Accelerate Testing

With the recent trend of organizations researching HPE testing alternatives, we’ve had a lot of questions about how HPE compares to Tricentis and what the migration process involves. We’ve outlined some technical details in a recent Fact Sheet, FAQ, and on-demand webinar, but we thought it would also be helpful to share a specific customer example.

Background: 15,000 HPE UFT Tests, 10 Week Regression Tests, Unknown Risk Coverage

A large European insurance company recently decided to migrate from HPE UFT to Tricentis Tosca enterprise wide, and started the rollout by focusing on their most critical application portfolio. After transitioning to agile, the development team started releasing software on 2-week agile sprints, but their existing testing process couldn’t keep pace. They previously built a regression test suite of approximately 15,000 HPE tests, but it took 10 weeks to execute. Exacerbating the issue, regression test execution usually triggered thousands of false positives that had to be reviewed and resolved before the release.

They wanted to integrate regression testing into their Continuous Integration process, but it wasn’t feasible to even complete execution—much less keep the test suite in sync with the rapidly-evolving application.

Migrating the HPE UFT Tests to Tricentis Tosca

There were two main phases to the HPE migration process: importing the legacy regression test cases and optimizing the resulting test suite. First, to jumpstart the transition from HPE to Tricentis, the team used the migration utility that Tricentis provides.   It took a total of 5 hours to import their existing 15,000 HPE UFT regression test cases. The automated process successfully migrated approximately 75% of their existing test assets (objects, keywords, and test data). The imported tests were reviewed and adjusted over the course of 4 weeks.

Optimizing the Test Suite for Efficiency and Risk Coverage

Once the initial test case migration was completed, the team moved on to the test suite optimization phase. After completing a quick risk assessment, they used Tricentis Tosca’s risk-based test case design to perform two main rounds of risk-based test optimization.

First, they focused on reducing test redundancy—eliminating tests that did not contribute to their overall risk coverage. They discovered that they could eliminate approximately 60% of their existing tests without impacting their level of risk coverage.

In the next round, they focused on increasing their risk coverage as efficiently as possible. The risk assessment revealed that their existing test suite wasn’t effectively covering their most critical business risks. Their initial test suite achieved 35% risk coverage—which is close to what most of our customers achieve by creating test cases intuitively. Using risk-based test case design, they identified an additional 2,000 tests that would increase their test coverage, then they built those tests in Tricentis Tosca’s business-readable interface. The complete test suite could execute in 8 hours—and risk-based analysis also helped them identify a core set of “smoke tests” that could achieve high risk coverage (over 50%) within 12 minutes.

In the end, the organization ended up reducing their test suite size by approximately 55% and reducing test execution time from 10 weeks to 8 hours using distributed execution—all while increasing risk coverage to 82%.

Continued Integration with HPE ALM

Although the organization wanted to migrate their HPE tests, they decided to continue using HPE ALM to manage requirements and reporting. Using Tricentis Tosca Connect, they enabled bidirectional synchronization of artifacts (requirements, test results, etc.) across these platforms. This way, testers can use their functional testing tool of choice without losing any connectivity to the legacy HPE functionality that’s still meeting their needs.