One aspect that I like about Micro Focus UFT Developer is the ability to integrate it into a testing framework as a library.

They have LeanFT Library. This is the reason we choose this tool, we can It's because it can combine and integrate with any unit. 

There are many good things. Like it is intuitive and scripting was easy.  Plus the availability of experienced resources in India due to its market leadership.

The most valuable feature of Micro Focus UFT Developer is the flexibility to work with many different types of software.

Every single feature on offer is valuable and useful. As long as it's a web-based tool, you can use this to test the application.

The initial setup is very easy.

The solution is very scalable.

The product offers very good stability.

Our developers only use it for record and play. They use Java but don't need to understand much programming knowledge, so this helps. They don't check the end-to-end flow or regression, which is really only required when we have a new build, so it makes the job easier. It is also both mobile and Windows-based. The app development team has recommended the UFT Developer version, as this is cheaper. All our tests are run unattended, automated, and they run on remote servers. The Java and .NET programmers have said that "This tool is really good. We don't need to write any code, but it writes the code itself, only record and play. And it is simple, and it is not heavy; I mean, it doesn't have a large footprint, and it works well for us."

The most valuable feature for UFT is the ability to test a desktop application.

Integration with other IDs. It being in the IDs that the developers are using is big. Another big thing is my staff is mostly automators and they are very technical folks. Most of them have development backgrounds, so they are much more comfortable and familiar in IDs like Eclipse or Visual Studio then they are in UFT, which is where we are coming from.

The cost is the most important factor in this tool.

Feature-wise it's okay, and it's comparable with other tools. All of the features that we need for our testing are available. 

We have additional features such as reporting, and one other important feature, in UFT, is the AI-based object recognition plugin. This is a good feature in UFT.

I work a lot with guys who work with meta-mathematics, like applied maths and quantum mathematics. So for us, the most important feature is the ability to handle complex algorithms, such as fuzzy logic techniques which is the first step towards artificial intelligence in our field. The support for containerisation and continuous learning, adapting to our needs like support for DevOps practices, is paramount in our work.

The most valuable feature is the automation of test cases.

We use UFT Pro together with other test organization tools. There are many testers or developers that are not used to UFT. They haven't been using it in many other places. But when they've been working with it for a while and they see the complexity when you're doing real and tough test situations, then they see that this kind of tool is very, very good.

It is quite stable, and it has got very user-friendly features, which are important in terms of maintaining our scripts from a long-term perspective. It is very stable for desktop-based, UI-based, and mobile applications. Object repositories and other features are also quite good.

The ability to evaluate live applications in our production environment for unusual behavior and determine problem areas and solutions is the most valuable aspect of this solution.

I would say the most valuable is that we can get people started off really quickly on solutions because we've been partners with HPE for a long time and it helps us tailor the product to ours needs. When we have issues with something we can get support directly from HPE since we paid for it.

The fact that it works with a vast number of technologies works for us because our internal customers use the tool for testing a lot of different applications. That's probably the best feature that it has for us.

The solution helps to accelerate software testing automation. It will help to reduce lead time and increase productivity and efficiency. 

The test data management is very easy to use. It is a very valuable feature. The client application testing is relatively easy in UFT as well.

The most valuable feature is the possibility to code the test framework with C# and Java and therefore, use the development teams.

I believe the main feature for using it is the flexibility across different platforms. For example, I can use it whether it's Eclipse using any of the programming languages. The multi-platform usage of LeanFT is really useful.

LeanFT is used a lot more by our less experienced testers and developers who want to get more point-and-click type automation. Then obviously I also manage the automation team, so we use UFT for a ton of all of our XLC automation as well as anything with a UI. So we also bring it into our business functions as well. If we need to do clean-up, data entry, management of manual tasks where you're putting yourself in a UI scenario, we'll run scripts for that for productivity.

We pretty much use that to streamline workflow and enable productivity in a business context in our business unit as well as in our IT shop, so just reducing workload on IT people as well as testing. It's used pretty extensively beyond that.

The most valuable feature is stability.

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.

The most valuable features are the ability to customize, if needed, and to integrate with ALM because its our test management. The ability to implement with Jenkins for dev ops is also a valuable feature.

It was very interesting to see that once we began using the traditional UFT for functional testing, we received a lot of feedback from our development and testing teams that it's clumsy, not modern, and so on. But once we upgraded to UFT Pro, it was an easy adoption, even though it's a commercial product. In that sense, it supports our approach in agile and DevOps deliveries really well.

The most valuable feature is that we have a test automation solution that is really developer friendly. So, you have Java as a programming language. You have Eclipse or the Intel HAS IDE and you can really use the development tools. That's the best part out of it. You can also have this with Selenium or any other developer friendly solution, but UFT Pro also supports different technologies. So, you can test web applications, you can test Java applications, you can test Windows applications. And, most other tools, at least the free-ware solutions, only cope with one specific technology.

Another big feature is the integration with ALM. It's quite easy to start the test cases from ALM and to have the results in ALM. And it's also possible to make business process tests with Lean FT or UFT Pro. And I think all these parts together make it the best possible solution.

The most valuable feature for me is the number of protocols that can be tested. It not only tests Web, but also SAP, Siebel, .Net, and even pdf. That's a strong point of this tool because open source tools like Selenium can run only one protocol, like Web, for example. A lot of legacy systems do not use Web as their front end, however. They use a Windows-built .Net application or something else that is not web-enabled.

The most valuable feature of the solution is the number of plugins for object recognition. The predefined libraries allow us to automate tasks.

Since we started using the Quality Center for the integration of all Microsoft tools, things have been much easier for us. Whatever integration we use between the tools creates a complete package of one set of tools. Many of our customers use Jira and Confluence and we can see how these tools integrate even with these things.

The recording feature is quite good as it helps us to find out how things are working. 

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

The fact that it is so easy to go between UFT with its large install base and LeanFT. Whoever has used UFT will quite easily become productive with LeanFT, but with the added benefit of “shifting left”, to move testing closer to the development cycle.

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.

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.

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.

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