OpenText UFT One Reviews

It helps us consolidate our efforts. All of our projects are in there. We are also in the life science domain so we have many more compliance requirements which we have to adhere to. It has helped us automate our testing. We have also integrated it with our other tools such as JIRA and TFS. It's pretty good so far.

We look at service packs, what bugs they have and fixes. We just want to keep pace with where the industry is going, where the shift is in terms of quality assurance and requirement management. HP is very strong on the testing side, but in the last few years with the agile methodology it has lagged behind. It's slowly catching up and eventually it will get there, but we love the eco-system we're in and will continue to move forward.

It's stable

It's very scalable, a very robust kind of solution and we recommend it to anyone who's looking for a testing automation kind of tool.

We use an HPE partner for our support needs, but tickets do go to HPE eventually, level two, level three. We have never had an issue.

It's very straightforward.

UFT is a very mature product, but again, changes. This is a highly fast-paced, fast rolling field, and you have to keep up the pace with them. There are a lot of open source testers, and they do the job. UFT is a very capable tool compared to Selenium or other test tools available on the market. It can do the job is it cost effective? Investment is definitely on the higher side initially in terms of licensing cost.

UFT provides us with solid automation for our test cases.

Its ease of use means we've been able to ramp up non-technical users and have them understand how to do general debugging very easily.

Tighter integration between ALM and UFT, especially from a reporting perspective, for automation reporting. There's good integration in my opinion, but it just needs to be a little more rock solid.

We've been using it for around three and a half years.

For the most part UFT has been pretty good. Getting it to interact with ALM nicely has been a challenge for us sometimes.

It's been able to scale to our needs.

Good, sometimes a little slow, but overall pretty good.

We didn't have any other solution in place, and needed to have a much better solution than doing testing with Excel files.

It's straightforward.

HPE was one of the very few vendors that we actually had on the list. We went with HPE because my boss actually was very familiar with the product, and felt it fits our organizations needs extremely well.

Give it a shot, if you take the time to invest in it, it works.

The ease of record and playback as well as descriptive programming are the most valuable features of UFT (QTP). Also the feature for automating both Windows and web applications form a single console is not bad.

My previous organization used UFT extensively for automation more than 500 complex end to end regression tests with considerable savings in time and effort. We were able to achieve that with high degree of reusability.

The product should evolve to be flexible so one can use any programming language such as Java and C#, and not just VB script. Also, the dependency of browser windows to be opened on screen in order for the tool to recognize objects is a big deal breaker since most organizations mandate screen locking when leaving the systems unattended. If we can’t leave a test to run attended, the point of automation in itself becomes a question-mark.

I've been using it for more than 10 years.

There were no issues with the deployment.

We did have a few instances of browser crashing as well as the product crashing. While the product crashing was resolved with 4 GB of memory, the issue with browser crashing still happened with IE 11 and 12 browsers and no resolution was found.

UFT is pretty late to support latest versions of IE. Also I have seen a marked decrease in execution speed while the scripts grow.

I have not interacted directly with HP on the product support.

UFT setup is pretty straightforward.

We did it in-house.

It took about five years to break even. UFT is costly.

No other options were looked as we went straight ahead into UFT.

Go for the cheaper option of Selenium if your requirement is purely browser based testing. If not, go for UFT.

It allows me to perform all in one place--

• Regression tests (tests which check that the existing functionality of an application still works as it should after other parts of the application have been modified),
• Functional tests (to verify a specific action or function of code), and
• Service testing (automated testing protocol)

I was able to reduce regression and functional test times by 80%.

It could be improved with greater browser compatibility and more frequent updates.

Also, running a simple test is straightforward, but creating a framework that can be reused across other tests is complex and time consuming.

I've used it for three to four years.

I didn't encounter any issues with deployment.

When debugging code in UFT, it would crash, freeze and hang a lot.

We had no issues with scalability.

6/10

8/10

We previously used Selenium Webdriver.

We implemented it with our in-house team.

HP UFT cost a lot and there are other free tools that can do the same and much more.

I joined the company after the decision was made to use HP UFT.

If cost is not an issue, then UFT can be considered. There are other tools on the market that can do the same for less.

For us, object recording is the most valuable and most used feature.

We've used it just during a Proof of Concept period.

We noticed during our PoC that it needs parallel execution, not execution via ALM.

I used 11.5 two years ago, and I just updated to 12.51 one month ago, but I have not really used it yet.

There were no issues with the deployment.

There were no issues with the stability.

There were no issues with the scalability.

We previously used Selenium. Our clients choose their IDEs and I integrate for them.

It's hard to install the license seat because the web-based GUI is not user friendly.

I implement it with in-house teams.

The add-on I am using has limited resource on-line that makes it a challenge to use. Compared to Selenium, I prefer Selenium. However, I may want to see HPMC before I can make better suggestions.

We have multiple SAP systems and clients. UFT allows us to use one set of tests for all systems.

We are a worldwide organization with a complex financial authorization matrix. When changes were made to this matrix, we provided automated test scripts. More than 20,000 tests were executed in 1 week.

The current version is sufficient for our purposes at the moment. There were, however, some issues with deployment and the integration into Solution Manager.

We've been using it for three years. Our primary system is SAP and we use UFT through SAP Solution Manager as a third-party testing tool.

Again, we had issues with deployment and the integration into Solution Manager. These are mostly resolved and the current situation is stable.

There were no issues with the stability.

There were no issues with the scalability.

We do not have a direct support contract with HP. Our license is through SAP. Customer support is 10/10 for HP and 8/10 for SAP, but improving.

This is my first involvement with automated testing software.

The initial set up was straightforward once we cleared up some communication issues. The first end-to-end automated test was functional within a week.

We implemented it through a SAP team, but now manage all maintenance and upgrades internally.

The license for this product is provided through our support contract with SAP. Any other product would incur additional license costs.

My only experience is with the product fully integrated with SAP. We are not licensed to use this as a standalone product we must connect to SAP.

The most valuable features of UFT to me are:

• UFT best supports automation of desktop based applications like AS400 apps, Java apps, SAP application, etc.
• UFT comes with built-in test frameworks like BPT. Using these frameworks test development can be started within no time.
• Lean FT provides the flexibility to the users to code in Java.
• UFT provides the flexibility to run the same tests against a variety of browsers like Chrome, Firefox and IE.

Manual execution of tests is always time consuming. With the help of UFT, the test execution time cycle was reduced from weeks to hours. This is essentially a giant leap. UFT framework enables to do easy and quick fixes to tests so that automation suite can still be run in case of changes in application. This feature is essentially very important for agile projects.

• Ability to run multiple Lean FT or UFT tests in parallel on the same machine.
• Lean FT to support desktop based applications as well.

I have been using HP UFT/QTP for the last 10 years.

There were no issues with the deployment.

UFT or Lean FT tests can only execute only one test on one machine. When the number of automation tests are very high, say 5000 to 10000, even with eight to 10 licenses, UFT can take over 24 hours for execution. This is unacceptable in agile projects. The regression test execution time is expected to be less than one hour for any agile project.

The customer service is prompt.

The technical support do not answer the questions to the point.

The initial set-up of UFT is quick and easy. The set-up instructions are straightforward and easy to understand. However, for a few applications such as AS400 and POS, the set-up requires a few installation steps to be followed in a specific sequence. If this is missed, then UFT may not recognize application objects at all.

I will always recommend setting up an in-house team with one test automation lead, one test automation architect and rest automation developers. However, if a vendor team offers a more cost effective solution, then the same team structure is to be implemented at their site.

For the QTP/UFT projects I have worked on ROI is always over 300% in the long term.

UFT offers a variety of licenses like seat licenses and concurrent licenses. If the automation team is small, say two to four, and fixed, node locked seat licenses would be preferable. Else, it is always advisable to go with concurrent licenses.

I have evaluated multiple paid and open source tools. I have evaluated paid tools like IBM Rational Functional Tester, TestComplete, Ranorex, Microsoft UI Automation, etc. Among these, HP UFT always tend to have better support for enterprise wide applications. However, if the requirement is to automate only a few applications, other tools can be considered. For web based application automation, Selenium WebDriver (open source) is the best automation tool.

It is always advisable to set the expectations right before starting any automation activity. Automation ROI is always negative for the first few months. The actual dividends of implementing automation will be reaped in the long term only. Also, automation is a continuous development/maintenance project same as application development. Without test maintenance, automated tests will not be useful in future.

• The most valuable thing in my opinion is the ease of moving objects for storage from AUT into the object repository and handling them. 
• Also, built-in features for database connectivity and SQL queries for data retrieval are a time saver. This eliminates the need for descriptive programming and writing huge chunks of code for relatively simple tasks. 
• Step delay and object sync options are also a very useful feature.

• It saves time and manpower. Test development and maintenance are faster and easier thanks to UFT. 
• Also, one tool covers several projects developed in different technologies while the approach to test design can remain the same. A relatively small team of trained professionals can cover a wide range of tests. 
• Due to UFT’s popup messages for errors and test execution results viewer, it is very simple to analyze the test results and figure out what went wrong, reducing the time needed for defect detection and test updates.

• When it comes to improvements, definitely stability and system requirements are something that could be worked on. In cases of longer tests (in forms of so-called Mega Scripts), there can be a seriously huge usage of virtual memory by UFT that can lead to SystemOutOfMemory exceptions which are showstoppers and a huge annoyance. 
• Object recognition can be tricky sometimes. For example, UFT doesn’t recognize the object during test execution, but when you pause the run and click “highlight in app” button in object repository it recognizes the object and you can continue with the run. You still get the “failed” status in run results although it was a UFT error.

We use UFT only for our own test automation needs.

We haven't had any issues with deployment.

See the stability issues we had above.

We've scaled it for our needs.

My advice would be to find at least one experienced automation developer who previously worked with UFT to provide practical know-how to others when implementing it for the first time. 

Learning the basics is easy and intuitive when you receive a proper training. But using UFT the wrong way can turn out to be cost ineffective. UFT is an expensive tool that can save you a lot of time and effort and provide great value for money if used correctly, but also turn out as ineffective related to value-for-money if used the wrong way. 

YouTube tutorials are not the best way of training people for using this tool, the best way is finding people who already have experience to work with it or provide proper training for employees who have never worked with it.