We performed a comparison between Apache JMeter and OpenText UFT One based on real PeerSpot user reviews.
Find out in this report how the two API Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I like the fact that JMeter integrates well with other tools."
"It gives accurate results and recommendations that we can implement to enhance the performance of websites."
"Apache JMeter is stable."
"We are using it just for load testing. We are using its free version, and it is scalable."
"I appreciate JMeter's simplicity and power for performance testing."
"It's a powerful tool that is open source."
"JMeter is easy to use for a user who doesn't have too much knowledge of programming or certain languages."
"When there's a high number of TPS I can achieve more transactions per seconds given the hyper-limitations."
"The most valuable features for us are the GUI, the easy identification of objects, and folder structure creation."
"The most valuable feature of Micro Focus UFT One is you are able to use it with many other technologies. I have not had an instance where the solution was not able to automate or execute automation. I was able to use COBOL to manage some automation."
"The solution has good out-of-the-box protocols."
"It is very simple to use, and the scripting language is even easier."
"The solution is easy to integrate with other platforms."
"It is easy to automate and new personnel can start learning automation using UFT One. You don't have to learn any scripting."
"On a scale of one to ten, I would give OpenText UFT One a 10 because it is a reliable product, it works, it's as good or better than similar solutions especially because you get technical support from real people. Additionally, upgrades are always provided on a consistent basis."
"The high-level security, high standard and compatible SAP are great."
"The UI of the solution needs to be better. The UI takes up a lot of our bandwidth."
"At present, if the number of virtual users increases beyond 10,000 when testing, then it results in a Java heap which causes the solution to crash."
"JMeter output reports can be difficult to understand without training."
"What needs improvement in Apache JMeter is the very high load requirements when you want to scale it beyond certain thresholds. For example, small to mid-range testing is very easily done with Apache JMeter, but if you scale and increase the load, then it would be a problem because the tool consumes a lot of resources, probably because Apache JMeter provides an enriched UI experience, so it consumes a lot of memory and requires high CPU usage. This means you have to manage your infrastructure, or else you'll have high overhead expenses. As Apache JMeter is a heavyweight tool, that is an area for improvement, though I'm unsure if Apache can do something about it because it could be a result of the way it's architected. What I'd like to see from Apache JMeter in the future is for it to transition to the cloud, as a lot of cloud technologies emerge around the globe, and a lot of people prefer cloud-based solutions or cloud-native tools. Even if a company has a legacy system, it's still possible to transition to the cloud. I've worked with a company that was an on-premise company that moved to the cloud and became cloud-native. If Apache JMeter could transition to the cloud, similar to k6, then it could help lessen the intense resource consumption that's currently happening in Apache JMeter."
"JMeter's reporting is extremely rudimentary. The fundamental reporting mechanisms need to be drastically improved. It doesn't utilize an automatic session management mechanism or methods other tools use like parsing cookies and variables. Everything needs to be done manually. There's no automation."
"There are certain things like we can't merge custom metrics into the JMeter reports. We're limited to JMeter metrics, and other server metrics can't be integrated with JMeter dashboard. This forces us to rely on another tool."
"Apache JMeter's UI can be made more colorful."
"In future releases, it would be helpful if there was an integration with ALM Octane."
"They need to reduce the licensing cost. There's pushback from customers because of the cost."
"Micro Focus UFT One could improve by having more maintenance. Every time when we run the solution and develop something, the next time when we run it it doesn't recognize the object. I have to redesign the object again and then run the solution. It's really a headache, it's not consistent."
"The UA objects are sometimes hard to recognize, so the coverage should be increased. Open-source alternatives have a broad scope. Also, it's sometimes difficult to make connections between two of the components in the UFT mobile center. It should be easier to set up the wireless solution because we have to set both. We directly integrate Selenium and APM, so we should try to cover all the features they have in APM and Selenium with the UFT mobile."
"Micro Focus UFT One could benefit from creating modules that are more accessible to non-technical users. Without a developer background or at least basic knowledge of VBScript, using Micro Focus UFT One may not be feasible for everyone. This is something that Micro Focus, now owned by OpenText, should consider in order to cater to business professionals as well. While Micro Focus UFT One does have a recording function, it still requires a certain level of IT proficiency to create effective automation, which may be challenging for those outside of the technical field."
"We used to run it as a test suite. Micro Focus provides that in terms of a test management tool as ALM, but when we think of integrating with a distributed version control system, like Jenkins, there isn't much integration available. That means we need to make use of external solutions to make it work."
"There is a lot of room for improvement when it comes to friction-free continuous testing across the software life cycle, as a local installation is required to run UFT."
"The product should evolve to be flexible so one can use any programming language such as Java and C#, and not just VB script."
"Needs to improve the integration with the CI/CD pipeline (VSTS and report generation)."
Apache JMeter is ranked 3rd in API Testing Tools with 82 reviews while OpenText UFT One is ranked 4th in API Testing Tools with 89 reviews. Apache JMeter is rated 7.8, while OpenText UFT One is rated 8.0. The top reviewer of Apache JMeter writes "It's a free tool with a vast knowledge base, but the reporting is lackluster, and it has a steep learning curve". On the other hand, the top reviewer of OpenText UFT One writes "With regularly occurring releases, a QA team member can schedule tests, let the tests run unattended, and then examine the results". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, OpenText LoadRunner Professional and Katalon Studio, whereas OpenText UFT One is most compared with Tricentis Tosca, OpenText UFT Developer, Katalon Studio, SmartBear TestComplete and UiPath Test Suite. See our Apache JMeter vs. OpenText UFT One report.
See our list of best API Testing Tools vendors.
We monitor all API Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.