OpenText UFT Developer Reviews

What’s awesome about it is you can use the same language the developers already use.

LeanFT integrates with our developers work-flow. Our developers can now perform automation using familiar tools, programming language, and IDE. This helps get the whole team involved in test automation.

In the next release I'd like to see HP enable LeanFT to work with Sauce Labs. I know HP has their own solution, but it would be better if it were more integrate-able in the spirit of being more open-source, more friendly.

We haven’t been using it that long, but it has been stable for the last month we’ve been using it. It works as advertised thus far.

Very positive: seems like it’s a lightweight solution that's not going to impact what we were already doing as it's just a "wrapper" on top of what we already do.

Haven’t had any technical support yet, but the demo team was great.

We had used a lot of different applications and we needed to shift left to new development practices. So we ended up using Selenium without native Java. Unfortunately, before LeanFT, we ran into issues where Selenium couldn’t handle the functionality of all the applications.

It's very straightforward-- you just import a library like you would any other tool and go.

Smartbear.

To me, it has to be using the same tools that the developers already use and that it fits in with their workflow. Testers should be using the same tools as the developers, making the development process easier.

We use this solution with one of the software applications that we have in our company, where we are trying to automate the different scenarios or workflows that we have.

I would also like to see cloud-Ops.

The most valuable feature is the object repository. The objects get identified using the tool or where the different properties of the objects are being captured. 

Also, object identification is something that really fascinates me about UFT.

As I have only been using this solution for a few weeks, I am really not in a position to say what needs improvement. I need to use it more where I can explore all the available features. If I am not able to perform any operation, then I will be in a position to answer this area of improvement better.

In the next release, I would like to see integration with different cloud-based tools such as Azure. Microsoft already supports the internet. 

I have been using MicroFocus UFT Developer for a few weeks.

We use version 15.20 or 1A.

It's a stable product.

This solution is scalable. At this time we have one user in our organization.

We are looking forward to using this solution in the future. We use the trial version and the team is considering the paid version. We have to see how it goes.

I have not contacted technical support. I have not needed to, there have been no issues.

Previously, we explored a few other solutions. One was TesComplete from SmartBear, and the other was Katalon Studio.

The initial setup was straightforward. It was easy.

The configuration that I have on the machine is the latest one. I haven't faced any issues. 

It didn't take long to deploy.

I am not aware of the pricing.

With the experience that I have, I think that it's very good, and I would recommend this solution to others.

Again, with the knowledge that I have in the few weeks that I have been using it, I would rate this solution a seven out of ten.

We use UFT Developer during the application testing process.

The most valuable feature is the Object Model, where you can directly pull up the object as a global or a local. It does not require as much scripting.

A basic level of programming knowledge is definitely needed to use this solution. It would be improved by adding a drag-and-drop interface to help alleviate the coding. We are investigating solutions where a layperson, with an interest in automation, can begin to work with the tool.

I have been using this solution for one and a half years.

This is a stable solution and it is used perhaps three times per week.

We may increase our usage in the future but it depends on our clients and their requirements. If their operations increase then our usage will as well.

UFT Developer is easy to scale. I am not sure how many people use this solution in the entire company, although I can say that we have approximately nine people who use it in my group.

The technical support has been fine.

We are also working with Selenium, which is an open-source solution. We did not use another tool before these.

The initial setup is of medium complexity. The deployment took a little longer than we had expected. We had planned for one day and it took a few hours longer than that.

The deployment was done by four to five people from our in-house team. They are mainly IT architects.

The cost of this solution is a little bit high and we are considering moving to another one.

We are considering moving to Katalon Studio in order to save costs. I am also hoping that it will be easier for people with non-programming backgrounds to use.

This is a good solution and I recommend it. I also recommend using Selenium if people want to use a more web-based application.

Overall, Micro Focus UFT is a good tool, but it is a little bit expensive.

I would rate this solution a seven out of ten.

It's a complete pursuit and it's a logical pursuit working with HPE.

The benefits. We're trying to maximize our automation testing, so it's a new authorization for us and we have more time to ... If we automate the test, we have more time to do something else.

We push one button and the tests are completely executed at once, so just have to analyze and say it's okay. It would be nice if this could be entirely automated. For the moment, it's people who have to perform this task.

For now it's stable.

We have just started. We have one person who use it. We have in the future plans to expand it to the whole company.

They connected 2C and UC so we can use 2C for the test and UC for information.

LeanFT's been very good. It's a little more complex than standard testing products like the standard UFT. It's a little more developer oriented. I'm not really a developer per say, but I was able to pick it up fairly quickly.

I think the biggest issues that I've seen, and this is a personal view of mine, is that most of the HPE products have a common look and feel to them. I'd really like to see it be a little more customizable to a use and user standpoint. For example. I happen to be colors blind, so I'd like to see more vivid colors on the UI, and things like that. It would make it a little more flexible from the customer standpoint.

I was formally an HP employee, so I've used the HP products in the past. I also was a former Mercury Interactive employee who was acquired by HP.

It's been extremely scalable as far as the testing that we've done with our customers. They've all been really satisfied with the scalability of the HPE products.

We've gone through the standard customer support and it’s been good. It's not quite to the level that an R&D would be, because they really get really under the covers to fix things.

Since it was a slightly different way of doing things, it was a little complex. It was just the idea of ... this is something new that we have to understand. It wasn't like we're building on a product that already existed, it was right out of the box. It's fairly new, so it was a little more complex that way but R&D made it very easy.