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

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 (17th)
ReadyAPI
Ranking in Functional Testing Tools
14th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
37
Ranking in other categories
Performance Testing Tools (7th)
 

Mindshare comparison

As of April 2026, in the Functional Testing Tools category, the mindshare of OpenText Silk Test is 1.8%, up from 0.9% compared to the previous year. The mindshare of ReadyAPI is 1.9%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Functional Testing Tools Mindshare Distribution
ProductMindshare (%)
ReadyAPI1.9%
OpenText Silk Test1.8%
Other96.3%
Functional Testing Tools
 

Featured Reviews

JG
Manager of Central Excellence at Alpura
Easy to set up with good documentation and easy management of testing cycles
The solution allows for a complete test cycle. The management of testing cycles are easy. We have good control over test cases. We can capture functional testing very easily. We're actually able to accelerate testing now and have end-to-end cycles for testing. We didn't used to have these capabilities. It's easy to automate and accelerate testing. The product offers very good cross-browser testing capabilities. We can do continuous testing and regression testing.
PK
Lead QA Engineer at Msys Technologies
Experience effective testing with flexible licensing alongside pivotal insights on essential improvements
For non-functional testing, I focus on performance and security. For performance and security tests, I used REST API, SoapUI, and JMeter. These tools help us conduct thorough testing across these dimensions. I find ReadyAPI helpful especially in overcoming security issues, as we experienced slowness in the application after merging our JAR files. For instance, if a person wants to access a university database and encounters a timeout error, we learned through ReadyAPI that the issue was due to HTML protocol limits with the payload. We fine-tuned this process to display the expected data effectively. I consider ReadyAPI a cost-effective solution because it covers three verticals without needing to purchase separate tools for security, performance, or functional testing. ReadyAPI is a versatile tool for creating multiple testing frameworks and validating various parameters seamlessly. REST API is the tool I use to test all three types of articles, meaning I validate the APIs I send to my peers or clients for functional testing, and I also perform security testing to ensure the URL and data passed through multiple components adhere to policies and user privileges. This is done through functional security testing using the REST API tool, and for performance, I ensure that applications can be accessed simultaneously by multiple users without hindrance or slowness through thorough performance testing.

Quotes from Members

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

Pros

"It drastically reduced our manual regression efforts that is difficult to achieve in Agile model."
"The ability to develop scripts in Visual Studio, Visual Studio integration, is the most valuable feature."
"The Silk4J feature is the solution's most valuable aspect."
"The major thing it has helped with is to reduce the workload on testing activities."
"It's easy to automate and accelerate testing."
"With the help of SilkTest we've automated a bunch of routine regression tests, thus we saved our testing team weeks of testing time."
"It is a fine product; it is a powerful tool, and it needs commitment."
"The major thing it has helped with is to reduce the workload on testing activities."
"Technical support from SmartBear is commendable."
"The main advantage is that it could be integrated into different CI/CD tools, and that is something that is really valuable and helpful."
"ReadyAPI is one of the best tools to use; it is easy to learn, easy to work with, and the features are very good."
"It's great for those that don't have as much exposure to programming."
"ReadyAPI's best features are that it's user-friendly and its behavior-driven development is flexible."
"ReadyAPI enhances my workflows by allowing us to use Docker containers based on the ReadyAPI test runner."
"It's easy to learn how to use it."
"ReadyAPI is one of the best tools for API testing because they have made a single platform for functional testing, load testing security, and also service actualization."
 

Cons

"The browser based testing needs to be improved."
"Implementing a better integration with Git. It was extremely painful to implement the link from Silk Central to Git."
"GUI interface could be simpler for non-developers."
"The pricing is an issue, the program is very expensive."
"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 initial setup is somewhat complex if you're deploying on-prem."
"The support for automation with iOS applications can be better."
"In terms of features, I have already raised different change requests on the ReadyAPI side. One of the largest functions I've requested is the validation of the payload for the REST APIs."
"ReadyAPI could improve by having dynamic validation information."
"There are lots of options within the solution, however they are not upfront or user-friendly."
"Based on my experience, ReadyAPI could improve by simplifying the process of scripting."
"It doesn't have connectors to the NoSQL database. This is one of the things where they do not have a very solid strategy today. Other solutions have an in-built mechanism where I can directly and easily connect. An API is more around a user submitting a request on the frontend. It then hits the backend, puts the data, and responds back. If I am hitting MongoDB or NoSQL databases, I do not have ready-made inbuilt solutions in ReadyAPI that can easily help me in automating it faster. In our organization, we deal with NoSQL databases, and therefore, we need Groovy. We just cannot have a connector from ReadyAPI to do that. I have to write Groovy scripts. If you have themes that are predominantly using MongoDB, it leads to more maintenance and support activity because we are introducing more code into our commission. In terms of additional features, it can have cloud support. This is one of the things where we are getting into cloud support. We'll see how it works, but it is one of the doubts that we still have."
"The product could be improved by including an inherent feature for UI automation."
"Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions."
"To generate a test suite in API, I had to create a separate one each time because otherwise it was just override the test. Each API had to be added separately. I thought I could just have one and then create different methods, but I had to add each API separately to create the test for that. That is an area that could be improved."
 

Pricing and Cost Advice

"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."
"We paid annually. There is a purchase cost, and then there is an ongoing maintenance fee."
"ReadyAPI is moderately priced, with added costs for more plugins."
"We have approximately 12 licenses in place. There are other solutions that are more expensive than ReadyAPI that have more features, but if the scope of the project is limited to SOAP and REST service, then this is the best option."
"It costs approximately $200 000 Taiwan Dollars for three years."
"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."
"The price of the solution has been fine."
"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 pricing is very competitive."
report
Use our free recommendation engine to learn which Functional Testing Tools solutions are best for your needs.
891,869 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
13%
Construction Company
10%
Healthcare Company
6%
Financial Services Firm
16%
Insurance Company
8%
Manufacturing Company
8%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise10
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise5
Large Enterprise28
 

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?
One issue I found with ReadyAPI is related to event listeners compared to JMeter or SoapUI. We created an in-house dashboard to display automation runs across projects, which required manual updati...
 

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: April 2026.
891,869 professionals have used our research since 2012.