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 statistics that are available are very good."
"The feature I like most is the ease of reporting."
"The ability to develop scripts in Visual Studio, Visual Studio integration, is the most valuable feature."
"A good automation tool that supports SAP functional testing."
"The major thing it has helped with is to reduce the workload on testing activities."
"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 features of ReadyAPI are the drag-and-drop options and the integration with versioning tool solutions, such as Git."
"The feature that allows you to import an API collection or a project is valuable."
"ReadyAPI's best features are user-friendliness, smooth integration with Postman, the speed of creating test cases, and integration with customer data."
"The initial setup of ReadyAPI is straightforward."
"It's great for those that don't have as much exposure to programming."
"The great thing about ReadyAPI is that it has a wide variety of functions. You can test any API that you come across. You are not limited to one type of API. It supports many APIs."
"The most valuable feature has been the assertion as a test step as this has allowed us to increase the scope of testing and validation."
"The interface is ok and they have the ability to re-load tests so that you can reuse them."
"They should extend some of the functions that are a bit clunky and improve the integration."
"The pricing is an issue, the program is very expensive. That is something that can improve."
"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 support for automation with iOS applications can be better."
"The solution has a lack of compatibility with newer technologies."
"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."
"What needs improvement in ReadyAPI is its load testing feature because there was a hiccup when my team performed some load testing on the tool. My team had meetings with the ReadyAPI team and tried to get that issue fixed, but it still hasn't improved. This is a shortcoming of the tool, especially when you compare it with HP LoadRunner."
"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."
"Better compatibility or more support for the older versions would be helpful."
"ReadyAPI could improve by adding a conversion tool from one file type to another. Import support for multiple file types would be beneficial."
"ReadyAPI could improve by having dynamic validation information."
"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."
"The reporting in ReadyAPI could be better. It can become sloppy, sometimes it works and other times it does not."
"There is room for improvement in ReadyAPI, particularly in the user interface."
Earn 20 points
OpenText Silk Test is ranked 26th in Functional Testing Tools while ReadyAPI is ranked 6th 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 OpenText UFT One, Selenium HQ, OpenText UFT Developer, Apache JMeter and froglogic Squish, whereas ReadyAPI is most compared with Apache JMeter, Katalon Studio, Tricentis Tosca, ReadyAPI Test 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.