OpenText UFT Developer Reviews

Basically, before LeanFT was introduced by HPE, I was looking at a solution similar to Selenium to integrate some scenarios that UFT was doing well for us; we had to look for other solutions with LeanFT-like leverage. The most important thing about LeanFT is that it gives us the opportunity to introduce developer testing. Initially, because UFT was VBScript based and because of the infrastructure, developers wanted to contribute toward testing, but could not, so they used VBScript and went to eLanguages, which they can use with their development like Java or C#.

They can use the same language that they're using for their unit testing, so they can contribute to that in the very beginning of the lifecycle instead of after the application has been fully developed, at which point it is tested and comments are made on the features.

That is the main aspect: we can put the developer into the testing scenario.

Initially, although they developed some in-house tools, we were looking for a third party to lower the speed provided. With LeanFT, we are trying to create a kind of hybrid infrastructure where we can use our existing scripting and in the same infrastructure we can use LeanFT.

I think the one thing we're basically asking for should be JavaScript support, but I think they will start adding JavaScript support in the future. We haven't moved into that; we’re still into LeanFT. We're still finding out what's in there. Once we know what we can really do in LeanFT, then I think we can start providing feedback regarding enhancements we want to see in the solution.

LeanFT is very new to us (we started six months ago). We are still in the process of using it and converting our scripts with it. That means we still need to see all of the built-in capabilities, but it is getting better and better.

Obviously, we are planning to scale in the future because with LeanFT via the service pack, we can do user checking with continuous integration tools, which was initially not possible with the UFT, so we are trying to convert as many scripts from UFT to LeanFT. It will give us the most flexibility with more ways of working with the CPU.

Technical support has been good so far. Sometimes it takes minutes, sometimes they take more time, but most of the time they're good.

We are doing a lot of testing and there are some scenarios where UFT does not fit into the scenario. Since then, we have been looking for a solution. Initially, we were looking at an open-source solution such as Selenium or some third-party tool to learn. We also wrote some of in-house processes, but they are not getting combined with ALM into the single repository, so we are looking for a sub-solution. We kept telling HP that we needed a solution; otherwise, we had to move from UFT and ALM. Ultimately, they told they came up with LeanFT and you can use it with either Eclipse or Visual Studio code.

I won't say initial setup was complex, but it was not clear how to setup because there was an issue with the licensing. The same licensing was not working with UFT that used to work before, but we got in touch with HP customer support, they got back to us and since then it has been very smooth sailing.

It depends on whether you already have a testing tool that is based on a different infrastructure, such as UFT or Selenium. Then, see how smooth the transition will be. However, to start from scratch, start with LeanFT as opposed to another solution because it can give you the power of managing your tests in ALM and the single repository so you don't have to worry about it. Once you install it, it is kind of the best tech with web-based infrastructure, so you don't have to worry about quality control and so on.

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.