OpenText Functional Testing and ReadyAPI compete in the software testing category. While OpenText Functional Testing is favored for its extensive technological support and enterprise preference, ReadyAPI offers superior API testing efficiency and integration with CI/CD tools.
Features: OpenText Functional Testing provides integration with DevOps, a record and replay function, and a codeless test automation feature, supporting diverse technologies. ReadyAPI ensures seamless API testing, easy environment customization, and supports multiple API types, with strong collaborative features and advanced scripting options.
Room for Improvement: OpenText Functional Testing needs cost reduction, better stability, improved browser compatibility, and enhanced AI features. Relying on older VBScript technology is a noted issue. ReadyAPI could use improved load testing, better version control integration, and a refined user interface.
Ease of Deployment and Customer Service: OpenText Functional Testing mostly requires on-premises deployment and faces challenges with technical support responsiveness. ReadyAPI also primarily uses on-premises deployments, with mixed reviews on customer service, though some users report fast issue resolution.
Pricing and ROI: Both solutions are costly. OpenText Functional Testing has a complex licensing model but is valued for its comprehensive scope. ReadyAPI, with a flexible licensing option, is seen as more cost-effective for API testing, despite a high price point.
The development time using UFT can be cut down into half as compared to coding from scratch.
Automation is done very fast, leading to improvements in the QA process and reducing the time needed for test automation.
We can easily achieve a return on investment in one, two, or three years.
Organizations can't wait for this lengthy process, especially when they are under pressure with their timelines.
Support cases are easily created and attended to promptly, depending on urgency.
The technical support is rated eight out of ten.
SmartBear had an ALM tool that helped manage project documentation, including Jira-related specifications, test plans, and test cases.
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.
I rate ReadyAPI between five to six for scalability due to complexities associated with scripting.
ReadyAPI's performance testing capabilities can impact API scalability assessments.
One of the key stability issues was that Windows would consume memory without releasing it, leading to regression testing crashes.
Once all configurations and preparations are done, it is very stable.
Incorporating behavior-driven development tests would enhance the capabilities of UFT One.
We frequently encountered stability issues when the browser dependency caused Windows to consume memory without releasing it, leading to crashes during regression testing.
If it could move closer to a no-code or low-code solution, it might dominate the market again.
One issue I found with ReadyAPI is related to event listeners compared to JMeter or SoapUI.
I'm considering the use of AWS and its Lambda functionalities prepared by the vendor.
There are many open-source tools with no cost, and there are no-code tools that are less expensive than UFT.
The pricing or licensing policy of OpenText is a bit expensive, however, it's one of the best solutions in the market.
It's cheaper than Tricentis Tosca but more expensive than some others.
The pricing of ReadyAPI is reasonable, considering its functionality compared to other tools in the market.
Currently, we don't extensively use the performance testing due to license costs.
UFT supports Oracle, SAP, PeopleSoft, and other non-web applications, making automation feasible.
OpenText Functional Testing has an impressive ability to connect to mobile devices and its ability to test so many different types of software, whether it be mainframe, APIs, mobile, web, or desktop.
The best features of OpenText Functional Testing include descriptive programming, the ability to add objects in the repository, and its ease of use for UI compared to other tools.
It also aids in faster feedback to developers, allowing them to implement developments in a sprint without the need for extensive testing afterwards, thus improving our time to market metrics.
ReadyAPI is a versatile tool for creating multiple testing frameworks and validating various parameters seamlessly.
ReadyAPI is valuable for web service automation and allowing us to generate test cases and automate processes.
| Product | Mindshare (%) |
|---|---|
| OpenText Functional Testing | 7.1% |
| ReadyAPI | 1.9% |
| Other | 91.0% |
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 13 |
| Large Enterprise | 74 |
| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 5 |
| Large Enterprise | 28 |
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.
ReadyAPI stands out for its API testing capabilities and integration with development tools like Jira and Git. Its user-friendly interface and automation with Groovy scripting make it a suitable, efficient choice for developers aiming for seamless project management and test execution.
ReadyAPI presents a comprehensive suite for API testing, supporting functional, performance, and security tasks with minimal coding required. It offers robust integration with tools such as Postman and CI/CD processes, enabling users to manage and automate testing scenarios efficiently. Despite its strengths, users notice limitations in performance and cloud integration, especially in scalability and test management. While it facilitates data-driven testing through Excel and supports on-premise and cloud environments, ReadyAPI could benefit from improved reporting and simpler scripting processes. Its interface and GitHub integration would further enhance its adaptability for larger projects and diverse applications.
What are ReadyAPI's main features?ReadyAPI is principally leveraged by industries that require precise API testing capabilities, spanning functional, performance, and security assessments. Its ease of integrating with CI/CD tools and ability to manage backend APIs make it an ideal choice in sectors that prioritize automation and reliability in testing processes. Companies operating within on-premise and cloud environments benefit from its support for diverse testing needs and scenarios, ensuring improved testing proficiency and response validation.
We monitor all Functional 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.
