

OpenText Functional Testing and Apache JMeter compete in the software testing category. OpenText holds an advantage in automation features for enterprise applications, while Apache JMeter leads in cost efficiency and ease of use for smaller projects.
Features: OpenText Functional Testing integrates with desktop, mobile, and API testing, offering versatile automation frameworks such as BPT. It provides extensive application coverage tailored for enterprise environments. Apache JMeter excels in load and performance testing with support for simultaneous user requests. It's lightweight, open-source, and compatible with various CI/CD pipelines, offering numerous plugins for customization.
Room for Improvement: OpenText struggles with high memory use, slow execution, and complex object identification. Users desire better browser compatibility, expanded language support beyond VBScript, and enhanced UI features. Apache JMeter's limitations include large-scale load test handling, GUI functionality, and real-time report generation. Users expect it to improve in scalability, reporting, and protocol support.
Ease of Deployment and Customer Service: OpenText is mainly deployed on-premises and requires skilled IT staff for setup, despite having generally positive technical support, though response times may be slow. Apache JMeter offers flexible deployment across on-premises and cloud environments, benefiting from community-based support rather than formal customer service structures.
Pricing and ROI: OpenText Functional Testing is costly, suited for large enterprises needing comprehensive application testing and integration, resulting in long-term benefits. Apache JMeter's open-source model provides considerable savings by eliminating licensing fees, making it appealing for organizations seeking high ROI with minimal operational costs.
With Apache JMeter, I have gained great statistics for performance and server metrics.
I have not seen a return on investment right now, as there is no improvement in Apache JMeter and reduction in cost, but I save time and reduce costs with Apache JMeter.
Automation is done very fast, leading to improvements in the QA process and reducing the time needed for test automation.
The development time using UFT can be cut down into half as compared to coding from scratch.
We can easily achieve a return on investment in one, two, or three years.
With AI models ChatGPT, troubleshooting issues has become very easy for us.
The support for Apache JMeter is excellent.
Apache JMeter has strong support through its vast Java-based community on platforms like Stack Overflow.
Support cases are easily created and attended to promptly, depending on urgency.
After creating a ticket, it takes three to five days for them to acknowledge it and then send it to somebody.
The technical support is rated eight out of ten.
We do have some methods where we can distribute the complete load between multiple systems and then try to do our testing.
JMeter is highly scalable, easily handling increased loads through the use of multiple servers.
This restricts the number of users and necessitates increasing load agents or distributing the script across multiple machines.
Running them in parallel allows you to consume multiple runtime licenses and just execute the tests that don't have conflicting priorities and get through a lot of volume much quicker.
The tool can be installed on all computers used by developers or test automation engineers.
JMeter performs exceptionally well, especially in non-GUI mode, which supports high loads efficiently.
Several necessary features still need improvements, specifically in terms of reports and additional functionalities compared to other commercial tools.
Previous versions of Apache JMeter were a little unstable, but the new versions are very stable.
One of the key stability issues was that Windows would consume memory without releasing it, leading to regression testing crashes.
With AI becoming more prominent, they can implement features where it can generate code by itself based on the results or provide suggestions.
Currently, we need to use multiple separate JMeter instances to simulate reductions in load, which isn't ideal.
The tool needs improvements related to client-side metrics, integrating with tools like YSlow or HTTP Watch, and enhancing mobile testing capabilities.
Incorporating behavior-driven development tests would enhance the capabilities of UFT One.
If it could move closer to a no-code or low-code solution, it might dominate the market again.
We frequently encountered stability issues when the browser dependency caused Windows to consume memory without releasing it, leading to crashes during regression testing.
Using JMeter helps us avoid additional costs for high-load testing since it is open-source and allows for unlimited virtual users at no extra cost.
My experience with pricing, setup cost, and licensing is that the cost and license are free because Apache JMeter is open source.
It's a cost-effective solution.
It's cheaper than Tricentis Tosca but more expensive than some others.
The pricing or licensing policy of OpenText is a bit expensive, however, it's one of the best solutions in the market.
There are many open-source tools with no cost, and there are no-code tools that are less expensive than UFT.
JMeter facilitates scripting capabilities, which include options for Groovy scripts.
It's useful for both the person conducting the test and the higher management, like project managers or senior executives, who may not know about the test.
Despite being open source, it offers features comparable to paid tools.
UFT supports Oracle, SAP, PeopleSoft, and other non-web applications, making automation feasible.
The object repository is one of the best in the market, allowing creation of a repository useful for all tests.
OpenText UFT One offered valuable features by allowing us to build up libraries to streamline repetitive tasks, making scripting much easier.
| Product | Mindshare (%) |
|---|---|
| Apache JMeter | 6.2% |
| OpenText Functional Testing | 13.2% |
| Other | 80.6% |

| Company Size | Count |
|---|---|
| Small Business | 27 |
| Midsize Enterprise | 25 |
| Large Enterprise | 56 |
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 13 |
| Large Enterprise | 71 |
Apache JMeter is a versatile, open-source tool designed for performance and load testing, widely recognized for its user-friendly interface and robust test automation capabilities. It supports a range of protocols and integrates seamlessly into various environments, making it ideal for high-load scenarios.
Apache JMeter stands out in performance testing for its ability to handle high transactions per second and perform distributed load testing effectively. Its open-source nature and cost-effectiveness are enhanced by its user-friendly GUI, which simplifies the testing process. Despite memory consumption concerns, Apache JMeter remains a top choice due to its large community support, comprehensive scripting capabilities, and easy integration with CI/CD pipelines, allowing for continuous automated testing. Its robust protocol support meets diverse testing needs.
What are Apache JMeter's key features?In industries like finance and banking, Apache JMeter is used extensively for performance validation to ensure system robustness under heavy user loads. It's integrated into CI/CD pipelines for automated testing processes, allowing organizations to simulate real-world scenarios and ensure high-performance standards.
OpenText Functional Testing provides automated testing with compatibility across technologies, browsers, and platforms. It targets APIs, GUIs, and applications like SAP and Oracle for efficient test automation, emphasizing usability and integration with tools such as Jenkins and ALM.
OpenText Functional Testing offers wide-ranging automation capabilities for functional and regression testing, API testing, and automation across web, desktop, and mainframe applications. It supports script recording and object identification, appealing to less technical users. Despite its advantages, it grapples with memory issues, stability concerns, and a challenging scripting environment. Its VBScript reliance limits flexibility, generating demand for enhanced language support and speed improvement. Users appreciate its role in continuous integration and deployment processes, managing test data efficiently, and reducing manual testing efforts.
What are the key features of OpenText Functional Testing?In industries like finance and healthcare, OpenText Functional Testing is leveraged for end-to-end automation, ensuring streamlined processes and accuracy in testing. Many companies utilize it for efficient test data management and integrating testing within continuous integration/deployment operations.
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.