We performed a comparison between Apigee and ReadyAPI Test based on real PeerSpot user reviews.
Find out in this report how the two API Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."There is plenty of support documentation available."
"They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs."
"It has all the features necessary to work in anything from a basic scenario to advanced applications."
"Apigee has proven to be one of the best of the breed."
"The initial setup was easy - there was an onboarding document with steps that we followed."
"Lifecycle management."
"I simply like how you can personalize your products and put them into product categories. That's what I like the most."
"Great flexibility with its features."
"The out-of-the-box support for the database is a valuable feature."
"SoapUI is uncomplicated and user-friendly."
"The product allows us to uncover any potential issues early on."
"The tool’s scalability is very good."
"SoapUI Pro is a good tool when it comes to API design and orchestration. Additionally, it is beneficial for functional and for performance testing."
"It's a very simple solution to use."
"One good feature is SoapUI's URL check, which allows you to check among the applications. I'm not just talking about the ones for Android. It has all kinds of multi-world tests that are really helpful."
"The Pro and free version of SoapUI Pro has good technical support."
"Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud."
"Integration should be improved."
"We are experiencing issues with automation; the production in Apigee is quite time-consuming."
"Areas like traffic handling of incoming requests, security features between third-parties and Apigee, and between Apigee and internal network servers, resources, or JSON areas, etc."
"It needs predictive analysis of consumption."
"I would like to see SOAP services and socket-based connectivity developed."
"I would recommend this solution to those who want to start using it, but it depends on the requirements and automation."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"Stability has been an issue for us. It needs to be looked at and made a bit better."
"We tried automation but it's not easy to integrate with the synching and some of the mission tools that we use for automated testing of APIs."
"The documentation needs to be improved because the interface is not easy for a first-time user."
"There are no bugs or glitches, but a few features available only in the Pro version could be made available in the open-source version. Some of the features do not necessarily need to be only available to Pro users. The data generator would be really useful for the open-source version users."
"Grouping of the cases is not possible in SoapUI, to my knowledge. When working with critical cases or the, we were not able to group them properly. We can definitely create a suite and add them there, but within a whole suite, we have to identify them, which was not easy."
"The UI should be improved."
"It is limited to scope and risk services only. It does have some support for JMS, but it is not out-of-the-box; you have to do some tweaks here and there."
"SoapUI would benefit from some more customization abilities. It's a good interface, but it would be nice if they added the ability to build custom dashboards where the user can do their own bar graphs and pie charts."
Apigee is ranked 7th in API Testing Tools with 82 reviews while ReadyAPI Test is ranked 8th in API Testing Tools with 31 reviews. Apigee is rated 8.2, while ReadyAPI Test is rated 8.0. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of ReadyAPI Test writes "Has out-of-the-box database support and can be easily used by non-technical staff ". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, WSO2 API Manager and MuleSoft Anypoint API Manager, whereas ReadyAPI Test is most compared with Postman, ReadyAPI, Broadcom Service Virtualization, Tricentis Tosca and Katalon Studio. See our Apigee vs. ReadyAPI Test report.
See our list of best API Testing Tools vendors.
We monitor all API 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.
