Try our new research platform with insights from 80,000+ expert users

OpenText Functional Testing for Developers vs Perfecto comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 28, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

OpenText Functional Testing...
Ranking in Functional Testing Tools
11th
Ranking in Test Automation Tools
9th
Average Rating
7.4
Reviews Sentiment
6.4
Number of Reviews
39
Ranking in other categories
No ranking in other categories
Perfecto
Ranking in Functional Testing Tools
14th
Ranking in Test Automation Tools
20th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
23
Ranking in other categories
Performance Testing Tools (15th), Mobile App Testing Tools (5th)
 

Mindshare comparison

As of February 2026, in the Functional Testing Tools category, the mindshare of OpenText Functional Testing for Developers is 3.1%, up from 2.7% compared to the previous year. The mindshare of Perfecto is 3.5%, down from 5.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Functional Testing Tools Market Share Distribution
ProductMarket Share (%)
OpenText Functional Testing for Developers3.1%
Perfecto3.5%
Other93.4%
Functional Testing Tools
 

Featured Reviews

Eitan Gold - PeerSpot reviewer
SQA Manager at Elmo Motion Control Ltd.
User-friendly integration with support for Visual Studio enhances GUI testing capabilities
OpenText UFT Developer is user-friendly and integrates well with Visual Studio. The support is excellent. It is easy to implement tests with OpenText UFT Developer. We primarily use it for GUI testing and testing web applications with another application. This is the main usage for us. We also integrate it with the N-unit Framework, and they work well together.
Roland Castelino - PeerSpot reviewer
QA Lead at BMO Financial
Its reporting allows us to have a clear view regarding what tests have been executed
The most valuable would be their Live Stream analysis, where I can see the live analysis of all the executions on a single device or multiple devices as well as track them. The live analysis and reporting would be the single most valuable feature. We leverage Perfecto’s reporting and analytics a lot. From the CI Dashboard, it is mainly the status, which is the past, failure count, and time consumption, e.g., how much time did an average test or script take? Along with that, it provides the historical view compared to the previous result, e.g., am I a pass or fail? Also, the stack trace is very important. Whenever a pass occurs, we don't look beyond that. However, whenever a failure occurs, the stack trace information that it gives us is pretty critical for us when figuring out where failures lie. It gives a summary for the pass/fail count, total test count, the historical view, time consumption for each test as well as the total tests, and the stack rate of the failure. Perfecto's analytics are very important since we use them on a daily basis. We run our executions daily. After every execution, we pull information from the Perfecto reporting system and share that with our stakeholders. Having this information accurately reported is pretty important for us, so everybody is aware of the current status of the product. That way, we can evaluate the health of the product or environment against that which has been executed. Therefore, it helps make those real-time decisions and highlights the impact to the business. I found Perfecto to be pretty easy to use while executing against cross-platforms. The main reason is because the same script or test automation where we execute on multiple platforms has minimal changes that I need to do. Also, it is easy for me to set up an execution on one platform, then on another platform, either in parallel or one after the other. Parallel opportunities save me time. Once the execution has been completed across these different configurations, I can always check and compare, e.g., what are the differences and consistencies? We utilize Perfecto’s cloud-based lab to test across devices, browsers, and OSs. I use it occasionally for manual testing. Though, there are other team members who use it more frequently than I do. I use it mainly for executing my automated tests. We have the Perfecto lab, cloud devices, and machines. I can program my test to execute against any of those devices, which gives me more confidence in my product. I can compare and see how my product or application functionally behaves across these different devices and from a UI point of view, which helps me a lot. The device lab is extremely important to our testing operations. We rely on having multiple devices up and running all the time. Whenever we kick off an execution, there are multiple reasons why executions may get triggered: * CodeCommit * A scheduled job. * Might be on-demand by any stakeholder. We need the lab to be available, as we need devices up and running for executions to take place. Also, the devices help since they allow us to have parallel execution, and not just wait for a sequential device to become free and available. Therefore, volume is definitely key. It also gives us an opportunity to compare execution across platforms in that space. It is extremely important to you that the lab provides same-day access to new devices since we analyze that data every single day after execution. Perfecto provides their own framework called Quantum Framework. That is one option. The other option is, if I want to have my own framework, I can have a Java-based Maven project, take a Selenium library, AppiumLibrary, and REST Assured library, and utilize the open-source framework. It is easy for us to connect to Perfecto, no matter what framework we use, as long as it has these core libraries in it. I can design and structure it any way that I want. The execution will happen in Perfecto no matter what since they have support for these tools or libraries. It is pretty neat that way. We are not dependent on using just one particular framework to use Perfecto. While there are still some framework limitations, there is the opportunity to use multiple, different open-source frameworks, then pass the execution to Perfecto. We can use most frameworks, then design and craft it any way that we want, then just pass the execution to Perfecto.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"Integrates well with other products."
"The most valuable feature of the solution is the number of plugins for object recognition. The predefined libraries allow us to automate tasks."
"OpenText UFT Developer works well with record technology, making it valuable for recording."
"The most valuable feature is the Object Model, where you can directly pull up the object as a global or a local."
"The most valuable features are the object repository."
"It is a product that can meet regulations of the banking industry."
"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."
"Perfecto has affected our software quality in a good way. It has allowed us to execute on-demand and on-choice. We also track the number of issues that we find in the product. Every single day, we tag the issues that we found. For example, if something was found by automation, that means it was found by a Perfecto execution. Over time, we realized the real value in tracking those numbers. We can see now that we have clearly been finding issues earlier. It has allowed us to catch our defects earlier, thus improving the quality of our applications."
"Mobile testing is the most valuable feature as it has reduced dependency on physical devices. We are located offshore and we don't have the physical devices, and shipping physical devices after every new release would be a difficult task. But with Perfecto, it is easy."
"We are able to offer a quality product that has been tested fully, which improves our customer satisfaction. That is a good thing. It has also reduced our IT infrastructure cost. We don't have to spend a lot on setting up infrastructure, which becomes redundant or obsolete very soon. It helps in offsetting that cost."
"It saves on the cost and effort of having to maintain our own virtual testing environment. Even our onshore team is not in the city that we work in, so that helps a lot. Even if we didn't invest a lot in getting multiple devices, having to share those devices would become a hassle."
"We're working in Agile and we need results ASAP. The fact that the lab provides same-day access to new devices is extremely important to us."
"I also like the reporting functions. We are constantly downloading these reports and sharing them with our final customers. They help us understand what kind of bugs are happening through the applications. The recording feature is handy because it lets us see a video of the process we run through the pipeline and discover the point at which the automation is breaking."
"It creates a faster production cycle and is quick to market. Things get deployed earlier because the testing happens on time. We can do a lot of panelization, so a lot of test phases can happen in a panel. People don't have to wait for a device to come to them. They can access multiple devices at the same time and do testing at the same time."
"We are continuously doing testing on different environments, devices, and platforms. It executes seamlessly on multiple devices without having any connectivity issues. It has been really helpful for us to test on cloud devices."
 

Cons

"Stability depends on the company's infrastructure and end-to-end infrastructure. When I used the tool in my project, we had a big problem with many users using it simultaneously."
"UFT Developer is good, but it requires high-level development skills. Scripting is something that everybody should know to be able to work with this product. Currently, it is very development intensive, and you need to know various scripting languages. It would be good if the development effort could be cut short, and it can be scriptless like Tosca. It will help in more adoption because not every team has people with a software engineering background. If it is scriptless, the analysts who wear multiple hats and come from different backgrounds can also use it in a friendly manner. It is also quite expensive."
"UFT is like a flagship of testing tools, but it's too expensive and people are not using it so much. They should work on their pricing to make themselves more competitive."
"In the next release, I would like to see the connectivity improved to be less complex and more stable."
"The parallel execution of the tests needs improvement. When we are running tests in LeanFT, there are some limitations in terms of running the same tests simultaneously across different browsers. If I'm running a test, let's say to log in, I should be able to execute it through IE, through Microsoft Edge, through Chrome, through Mozilla, etc. This capability doesn't exist in LeanFT. Parallel execution of the test cases across different browsers need to be added."
"It's now too heavy and they should be making it faster. We do an attempt at automatic regression testing. We schedule a test to start at a certain time. It takes a lot of time to download the resources and start UFT. Competitors in this area have tools that start faster and run the test faster. For example, if the test at our side will take 10 minutes, another tool will do that in one minute."
"There's room for improvement, especially when I compare OpenText to newer tools like NeoLoad."
"With Smart Bear products generally, you can have only one instance of the tool running on a machine."
"The flakiness, or the accuracy, of the test execution can be improved. Also, the responsiveness of their cloud lab could be improved as well."
"Previously, we used the cradle. Every time the mobile was blocking it, we would have to ask Perfecto to provide another one. That took a lot of time away from us."
"The monitoring features, in particular network traffic monitoring, could be improved."
"There could be some improvements done on the interface. At times, there has been a bit of a struggle when finding things on the interface. A UI revamp would be a better option in future. That UI hasn't changed much in a long time, so I think they could just make it a bit better so that people could find stuff easily and intuitively."
"I would like to see the inclusion of machine learning features. If we can have that, it will be a better tool."
"There was a discussion about having the capability to export the test results to a certain tool that we use in our project. If that were added it would be great not having to manually take screenshots, put them in a document, and share them on the different test management tools."
"I'm hoping they can support on-premises instances. We have been working on a JIRA integration with Perfecto—and I'm extremely impressed that they have that—but at this time they're not supporting onsite JIRA instances, which is what we have."
"When using devices on the cloud, it lags quite a bit at times. I know that these are real devices that are being projected on our laptop screens and monitors, but if the speed could be improved, that would be good."
 

Pricing and Cost Advice

"It is quite expensive and is priced per seat or in concurrent (or floating) licenses over a period of months."
"The price of the solution could be lowered. The cost is approximately $25 per year for a subscription-based license."
"The cost of this solution is a little bit high and we are considering moving to another solution."
"The licensing is very expensive, so often, we don't have enough VMs to run all of our tests."
"Its cost is a bit high. From the licensing perspective, I am using a concurrent license. It is not a seed license. It is something that I can use in our network. It can also be used by other users."
"The pricing is quite high compared to the competition."
"When we compare in the market with other tools that have similar features, it may be a little bit extra, but the cost is ten times less."
"If I would rate it with one being inexpensive and ten being expensive, I would rate pricing an eight out of ten."
"Pricing is an area where Perfecto can do a little better. When we obtain additional licenses, we enter into negotiations with them."
"This is an expensive solution compared to others, by 30% to 40%."
"Although Perfecto is a good product for us to use, it is a bit expensive. It takes management a bit of work to find the appropriate funding for us to keep Perfecto. I imagine there could be some way to make it more accessible."
"Perfecto is about 30-40% cheaper than Device Anywhere. That was a big reason why we switched. Perfecto also solves some of the issues that we had with Device Anywhere. We have grown by 100% since we started to use Perfecto, and now we have devices roaming. When we look at the competition, we would still stick with Perfecto."
"Perfecto's price is excellent compared to other products with similar features. It was the lowest of the three we evaluated. We also established a partnership with Perfecto, so they provide discounts when we sell Perfecto projects and licenses to our customers."
"Perfecto has definitely saved us on the costs and efforts of having to maintain our own virtual test environment. We lost about 20 devices in the past to maintenance and audit. That was a massive loss for us, as a company, because we were giving devices to someone, but don't know whether we would get it back or not. Having those virtual labs, we don't need to worry about these kinds of things. We are easily saving $5,000 to $10,000 a month on device costing."
"Pricing-wise, it is fine. It is not as expensive as what we used to have in the past from HP, IBM, and others. It is decently priced."
"It's definitely on the higher end of prices for this type of service."
report
Use our free recommendation engine to learn which Functional Testing Tools solutions are best for your needs.
882,032 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
13%
Performing Arts
8%
Computer Software Company
7%
Financial Services Firm
22%
Computer Software Company
10%
Manufacturing Company
8%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise12
Large Enterprise29
By reviewers
Company SizeCount
Small Business1
Midsize Enterprise1
Large Enterprise23
 

Questions from the Community

What is your experience regarding pricing and costs for Micro Focus UFT Developer?
The price of OpenText UFT Developer is a bit higher than expected, but there are no better tools available for a valid comparison.
What needs improvement with Micro Focus UFT Developer?
As of now, we don't have integration in the CI/CD pipeline, but they are supporting that as well. When your machine is in a locked state, you can even execute the Windows application automation. Mi...
What is your primary use case for Micro Focus UFT Developer?
For functional testing, we are using OpenText Functional Testing for Developers as our product for testing. I am using the cross-browser testing capabilities of OpenText Functional Testing for Deve...
Ask a question
Earn 20 points
 

Also Known As

Micro Focus UFT Developer, UFT Pro (LeanFT), Micro Focus UFT Pro (LeanFT), LeanFT, HPE LeanFT
Perfecto Mobile, Perfecto Web
 

Overview

 

Sample Customers

Walmart, Hitachi, American Airlines, PepsiCo, AT&T, Ericsson, United Airlines
Virgin Media, Paychex, Rabobank, R+V, Discover
Find out what your peers are saying about OpenText Functional Testing for Developers vs. Perfecto and other solutions. Updated: January 2026.
882,032 professionals have used our research since 2012.