We performed a comparison between OpenText Silk Test and ReadyAPI based on real PeerSpot user reviews.
Find out what your peers are saying about Tricentis, OpenText, Perforce and others in Functional Testing Tools."The scalability of the solution is quite good. You can easily expand the product if you need to."
"The ability to develop scripts in Visual Studio, Visual Studio integration, is the most valuable feature."
"The feature I like most is the ease of reporting."
"A good automation tool that supports SAP functional testing."
"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 statistics that are available are very good."
"The major thing it has helped with is to reduce the workload on testing activities."
"One of the features of ReadyAPI that's worth mentioning is that it allows you to parameterize. I'm working with more than two hundred resources, so I don't have to go and make a small change at each point every time. I have the option to just parameterize in one place for the changes to reflect everywhere. Another valuable feature of ReadyAPI is that it provides a customized environment. In my company, you work in different environments, such as QA, UAT, and LT, so the URLs for every environment are different. In ReadyAPI, you can customize your environment, set it up, then start working on it. Another feature worth mentioning that's offered in ReadyAPI is automating your test value as the tool allows Groovy scripting. In your test case, you can use a Groovy script that says that in a particular test case, you have ten resources, but you just want to exhibit five and that you don't want to exhibit the remaining five. You can write a small Groovy script that lets you execute just five resources out of the ten resources. I also like that ReadyAPI allows you to read the data from CFC and Excel. It also allows you to create or customize your data, but that only works at a certain point because every application has its specific data. ReadyAPI cannot generate every data, but when I'm posting and I want to generate a random name, such as a first name, I can do it in ReadyAPI. The tool also has many different features which I find valuable, including Git integration."
"When you are working in sprints, you need to have continuous feedback. ReadyAPI definitely helps in automating very fast and rapidly. We have less coding, and we can more easily define our assertions. We don't use it for full-blown performance testing, but normally if you are doing your functional testing, it gives you the request and response time. Anybody who is doing functional testing can see what the request and response times are and raise a flag based upon their business affiliates, that is, whether it is meeting their affiliates. You can identify this during functional testing."
"When we are doing API testing we have found it to be very efficient to receive results. Additionally, you are able to do tests directly from the API."
"This solution is very intuitive. Once you finish your first few testing cases, you can change several parameters and create lots of testing cases. You could use the same testing cases for different purposes such as automation, performance and screen testing."
"The two most valuable features we use are the functional test and the security test."
"I haven't seen any other tool that offers both types of tests. This is very helpful for us, and it's one of the main reasons why we chose this service."
"The Excel sheet feature is good."
"The feature that allows you to import an API collection or a project is valuable."
"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."
"Could be more user-friendly on the installation and configuration side."
"The solution has a lack of compatibility with newer technologies."
"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 Property Transfer capability could be more user friendly because it is a bit difficult to understand."
"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."
"Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions."
"Version control does not work well."
"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."
"I would like to see a better dashboard for monitoring in the next release of this solution."
"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."
"Areas for improvement include the security files, endpoints, and process sessions."
Earn 20 points
OpenText Silk Test is ranked 25th in Functional Testing Tools while ReadyAPI is ranked 8th in Functional Testing Tools with 34 reviews. OpenText Silk Test is rated 7.6, while ReadyAPI is rated 7.8. The top reviewer of OpenText Silk Test writes "Stable, with good statistics and detailed reporting available". On the other hand, the top reviewer of ReadyAPI writes "Allows you to parameterize in one place for the changes to reflect everywhere and lets you customize the environment, but its load testing feature needs improvement, and costs need to be cheaper". OpenText Silk Test is most compared with Selenium HQ, OpenText UFT One, OpenText UFT Developer, Apache JMeter and froglogic Squish, whereas ReadyAPI is most compared with Apache JMeter, Katalon Studio, ReadyAPI Test, Tricentis Tosca and SmartBear TestComplete.
See our list of best Functional Testing Tools vendors.
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.