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

OpenText Silk Test vs ReadyAPI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 18, 2024

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 Silk Test
Ranking in Functional Testing Tools
20th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
17
Ranking in other categories
Regression Testing Tools (8th), Test Automation Tools (20th)
ReadyAPI
Ranking in Functional Testing Tools
16th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
36
Ranking in other categories
Performance Testing Tools (7th)
 

Mindshare comparison

As of June 2025, in the Functional Testing Tools category, the mindshare of OpenText Silk Test is 0.9%, down from 1.3% compared to the previous year. The mindshare of ReadyAPI is 1.3%, down from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Functional Testing Tools
 

Featured Reviews

SrinivasPakala - PeerSpot reviewer
Stable, with good statistics and detailed reporting available
While we are performance testing the engineering key, we need to come up with load strategies to commence the test. We'll help to monitor the test, and afterward, we'll help to make all the outcomes, and if they are new, we'll do lots and lots of interpretation and analysis across various servers, to look at response times, and impact. For example, whatever the observations we had during the test, we need to implement it. We'll have to help to catch what exactly is the issues were, and we'll help to see how they can be reduced. Everything is very manual. It's up to us to find out exactly what the issues are. The solution needs better monitoring, especially of CPU.
Walter Wirch - PeerSpot reviewer
Seamless integration with cloud environments supports backend projects while seeking AWS Lambda enhancements
ReadyAPI enhances my workflows by allowing us to use Docker containers based on the ReadyAPI test runner. It helps extend our functional tests, even though we are not heavily using performance testing. It supports a wide range of protocols such as Kafka and GRPC, depending on the project. 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.

Quotes from Members

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

Pros

"The statistics that are available are very good."
"The feature I like most is the ease of reporting."
"A good automation tool that supports SAP functional testing."
"The major thing it has helped with is to reduce the workload on testing activities."
"The ability to develop scripts in Visual Studio, Visual Studio integration, is the most valuable feature."
"It's easy to automate and accelerate testing."
"The scalability of the solution is quite good. You can easily expand the product if you need to."
"Scripting is the most valuable. We are able to record and then go in and modify the script that it creates. It has a lot of generative scripts."
"The most valuable feature of ReadyAPI is that it is user-friendly."
"The dashboards are very good and consolidate all of the tests that you are performing with the client."
"It's easy to learn how to use it."
"ReadyAPI enhances my workflows by allowing us to use Docker containers based on the ReadyAPI test runner."
"The two most valuable features we use are the functional test and the security test."
"Reporting is more robust than other products because test reports can be exported in multiple ways."
"It's great for those that don't have as much exposure to programming."
"It is the best solution you can get across the globe for API, test automation, and API penetration testing."
 

Cons

"The support for automation with iOS applications can be better."
"The pricing is an issue, the program is very expensive. That is something that can improve."
"They should extend some of the functions that are a bit clunky and improve the integration."
"Everything is very manual. It's up to us to find out exactly what the issues are."
"The pricing could be improved."
"Could be more user-friendly on the installation and configuration side."
"We moved to Ranorex because the solution did not easily scale, and we could not find good and short term third-party help. We needed to have a bigger pool of third-party contractors that we could draw on for specific implementations. Silk didn't have that, and we found what we needed for Ranorex here in the Houston area. It would be good if there is more community support. I don't know if Silk runs a user conference once a year and how they set up partners. We need to be able to talk to somebody more than just on the phone. It really comes right down to that. The generated automated script was highly dependent upon screen position and other keys that were not as robust as we wanted. We found the automated script generated by Ranorex and the other key information about a specific data point to be more robust. It handled the transition better when we moved from computer to computer and from one size of the application to the other size. When we restarted Silk, we typically had to recalibrate screen elements within the script. Ranorex also has some of these same issues, but when we restart, it typically is faster, which is important."
"The solution has a lack of compatibility with newer technologies."
"Sometimes, if I changed something in ReadyAPI, it would not quickly pick up the change. It used to give me the same error repeatedly, and when I closed the application completely and restarted it, it would pick up that change."
"They have performance testing also. However, it's not that great."
"ReadyAPI can improve because it is limited to only SOAP and REST services. They should update the solution to include more protocols so that other people are not limited to SOAP and REST services. Other than would be able to utilize it."
"The solution is made up of multiple tools, and the one additional feature we'd like to have is load testing."
"ReadyAPI's customer support isn't that great, particularly their response time."
"The content on ReadyAPI in SmartBear Academy is outdated."
"It is challenging doing upgrades and patches because sometimes the environmental variables or suits in the projects get erased."
"The overall scope of this solution is limited and could be improved."
 

Pricing and Cost Advice

"We paid annually. There is a purchase cost, and then there is an ongoing maintenance fee."
"Our licensing fees are on a yearly basis, and while I think that the price is quite reasonable I am not allowed to share those details."
"The pricing is very competitive."
"This is a cheap solution when you consider the money that will be saved in testing."
"It is expensive. Each user needs to be licensed, and there are different licenses within the product. It starts with 750 euros for a single user per year, but for the full product features, you need to pay a lot more. There are three versions. This cost is for functional testing, and then there is a cost for load testing and virtual services. If you want to use these areas with the functional test license, you are limited. You hit some limits in these functions. If you have all three licenses, then you have full functionality for the API."
"The price of the solution has been fine."
"The solution is dynamically priced so you only pay for what you use."
"If I remember correctly, ReadyAPI costs between $5,000 to $7,000 for five thousand virtual users running it at a given point in time. Other tools, for example, Apache JMeter, can run millions of users at a given time. ReadyAPI is a tool that requires you to pay more money if you want more users to run it for performance testing. For functional testing, each ReadyAPI license costs $1,000, and you do get basic testing, and it's inclusive of one hundred users. In my company, if there's a need for more than one hundred users, my team uses Apache JMeter because it's futile to end up paying $5,000 or $6,000 annually just for performance testing, which can be done in Apache JMeter as well. Given the circumstances, my team does performance testing only towards the end of the fiscal year when the regulatory testing of applications takes place. If I have to run ReadyAPI just for two days or just for ten or fifteen odd days, then it's not worth paying $5,000 for the license with the small number of users provided by ReadyAPI."
"We use fixed licenses, and the last time I checked, I want to say it's around $680 per seat per year."
"The price was around $6,000 for one license, but I don't remember exactly. It is definitely expensive. Our organization was planning on having multiple licenses for this year."
report
Use our free recommendation engine to learn which Functional Testing Tools solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
17%
Manufacturing Company
10%
Retailer
6%
Financial Services Firm
21%
Computer Software Company
15%
Insurance Company
9%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for Silk Test?
The pricing depends on the license used. The pricing is similar to others in the market.
What is your primary use case for Silk Test?
The product is used for manual, functional, and performance testing. I'm using the tool for loading data into ERP systems.
What do you like most about ReadyAPI?
The performance testing capabilities are very good.
What is your experience regarding pricing and costs for ReadyAPI?
Currently, we don't extensively use the performance testing due to license costs. License prices can be a factor in considering which technologies to adopt.
What needs improvement with ReadyAPI?
In native teams and cloud environments, there is room for improvement. I'm considering the use of AWS and its Lambda functionalities prepared by the vendor. These are more so points from my wishlis...
 

Also Known As

Segue, SilkTest, Micro Focus Silk Test
Ready API
 

Overview

 

Sample Customers

Krung Thai Computer Services, Quality Kiosk, Mªller, AVG Technologies
Healthcare Data Solutions (HDS)
Find out what your peers are saying about OpenText Silk Test vs. ReadyAPI and other solutions. Updated: June 2025.
856,873 professionals have used our research since 2012.