No more typing reviews! Try our Samantha, our new voice AI agent.

OpenText Functional Testing for Developers vs Perfecto comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

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
6th
Ranking in Test Automation Tools
7th
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
20th
Ranking in Test Automation Tools
21st
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
23
Ranking in other categories
Performance Testing Tools (13th), Mobile App Testing Tools (6th)
 

Mindshare comparison

As of August 2026, in the Functional Testing Tools category, the mindshare of OpenText Functional Testing for Developers is 3.5%, up from 2.8% compared to the previous year. The mindshare of Perfecto is 2.5%, down from 4.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Functional Testing Tools Mindshare Distribution
ProductMindshare (%)
OpenText Functional Testing for Developers3.5%
Perfecto2.5%
Other94.0%
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

"Within a week, two of my global customers were able to leverage their automation through this solution, and the adaptability of how this slotted in was just amazing, which was incredibly efficient."
"LeanFT's been very 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."
"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."
"The most valuable feature is the automation of test cases."
"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.""
"Once we upgraded to UFT Pro, it was an easy adoption, even though it's a commercial product, and it supports our approach in agile and DevOps deliveries really well."
"To the business, I would say overall it increases the amount of testing that gets done, with more people interacting with automating."
"The Perfecto device lab has allowed us to run tests on multiple devices at the same time and across multiple platforms as well, increasing the efficiency of our testing and saving money, time, and effort while enabling comprehensive testing and high app quality that we otherwise wouldn't be able to achieve."
"Overall, it has definitely translated to cost savings and the reason is multifold."
"The reporting feature is really tough to find in some of the other products that are competitors. Having your CITB type dashboard, where we can see the test results and see recordings of each test that passed or failed, is probably one of the distinguishing aspects of Perfecto."
"The most valuable feature is automated testing."
"One of the good things about Perfecto is the scalability that it provides, as we are able to quickly scale up the devices and choose Android devices, web-based applications, or whatever we need, and we can scale up quickly and easily."
"The automated test reporting functionality is the most valuable feature. We use the CI Dashboard. It's very important as it is the main reporting tool for our automated tests."
"When the scripts are stable, Perfecto is awesome."
"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."
 

Cons

"There's room for improvement, especially when I compare OpenText to newer tools like NeoLoad."
"In the next release I'd like to see HP enable LeanFT to work with Sauce Labs."
"The solution could improve by working better with desktop applications and websites."
"The product has shown no development over the past 10 or 15 years."
"Object definition and recognition need improvement, especially with calendar controls. I faced challenges with schedulers and calendars."
"Ultimately, due to the scripting, integration, and other functionality that is missing, we may switch to another solution in the future."
"I would rate technical support a one out of five."
"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."
"It is slow compared to physical device testing. The interactive speed could be improved."
"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."
"The flakiness, or the accuracy, of the test execution can be improved. Also, the responsiveness of their cloud lab could be improved as well."
"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."
"It does well for mobile testing, but when it comes to the web aspect, it is lagging a little bit in terms of execution."
"Going by the dashboard or analytics capabilities that Perfecto or Perforce is looking to offer in its roadmap, it will certainly help if they also cater to executing and enabling decision-making, rather than just focusing on standard testing metrics such as execution, efficiency, and defect rate. These are good metrics, but they don't necessarily enable decision-making for SLTs. Any improvements in the dashboards and reporting tools should focus on metrics or SLAs that can help with decision-making."
"We feel that Perfecto is a little slow. If they could improve on that slowness in accessing the app, when we want to click a button, that would be great because we feel the difference. An improvement in the connectivity speed is required."
"We don't use Perforce's BlazeMeter with Perfecto. From my perspective, it's not really relevant."
 

Pricing and Cost Advice

"It is cheap, but if you take the enterprise license, it is valid for both software items."
"The cost of this solution is a little bit high and we are considering moving to another solution."
"It is quite expensive and is priced per seat or in concurrent (or floating) licenses over a period of months."
"If I would rate it with one being inexpensive and ten being expensive, I would rate pricing an eight out of ten."
"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."
"The pricing is quite high compared to the competition."
"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 licensing is very expensive, so often, we don't have enough VMs to run all of our tests."
"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."
"This is an expensive solution compared to others, by 30% to 40%."
"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 is an area where Perfecto can do a little better. When we obtain additional licenses, we enter into negotiations with them."
"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."
"I am not sure about its pricing, but from our perspective, licensing has been easy. Anytime I have new users or requests for users that want to get added, it's a very simple process. I just give the architectural owner of the product the name and email address, and they're able to easily add a new user. We don't have any issues in regards to getting licenses, but I don't have any insights into pricing."
"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."
"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."
report
Use our free recommendation engine to learn which Functional Testing Tools solutions are best for your needs.
907,731 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
11%
Construction Company
10%
Outsourcing Company
8%
Financial Services Firm
20%
Construction Company
12%
Outsourcing Company
7%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise12
Large Enterprise30
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: June 2026.
907,731 professionals have used our research since 2012.