TrustRadius Insights
SoapUI and its Pro version, ReadyAPI, are widely used tools for integrating, verifying, and testing web services. They are highly scalable …
Overview
What is ReadyAPI?
ReadyAPI (formerly SoapUI Pro, LoadUI Pro, and ServiceV Pro) is a REST and SOAP API functional testing tool that enables software developers, QA engineers, and manual testers to work together to create, maintain, and execute complex end-to-end API tests in…
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
N/A
Unavailable
What is ReadyAPI?
ReadyAPI (formerly SoapUI Pro, LoadUI Pro, and ServiceV Pro) is a REST and SOAP API functional testing tool that enables software developers, QA engineers, and manual testers to work together to create, maintain, and execute complex end-to-end API tests in their CI/CD pipelines without needing to…
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
16 people also want pricing
Alternatives Pricing
What is Tricentis Test Automation for ServiceNow (discontinued)?
Tricentis' solution for testing ServiceNow workflows, Tricentis Test Automation for ServiceNow, is a scoped application within the user's Now Platform, boasting a familiar interface equipped with a centralized dashboard to view test plans, suites, cases, and results.
What is Rapise?
Rapise is a software testing platform that allows users to regression test web, desktop and mobile applications. Some key features include: Playback of Tests, Test Script Editing and Data Driven Testing.
Product Demos
Demo Session: API and Webservices Testing and Automation Using SoapUI, ReadyAPI and Groovy
YouTube
ReadyAPI + Groovy: Data Driven tests with Rejseplanen’s API - Demo
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is ReadyAPI?
ReadyAPI (formerly SoapUI Pro, LoadUI Pro, and ServiceV Pro) is a REST and SOAP API functional testing tool that enables software developers, QA engineers, and manual testers to work together to create, maintain, and execute complex end-to-end API tests in their CI/CD pipelines without needing to code.
ReadyAPI Integrations
ReadyAPI Competitors
ReadyAPI Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Frequently Asked Questions
Reviewers rate Usability highest, with a score of 9.9.
The most common users of ReadyAPI are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(154)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
SoapUI and its Pro version, ReadyAPI, are widely used tools for integrating, verifying, and testing web services. They are highly scalable and configurable, allowing for custom test script creation and automation of various test activities. Users have found SoapUI useful in validating complex analysis platforms, establishing baselines for customization, and verifying APIs across multiple products with different interfaces like SOAP, REST, AMF, and JDBC.
Yahoo's Technical Account Management team relies on SoapUI to analyze SOAP messages and troubleshoot issues with ad platforms. Developers, integrators, and technical product managers use SoapUI for testing, automation, and support purposes. ReadyAPI is the go-to tool for API testing, making it easy to create and manage tests. It helps in verifying breakages, tracing back problems to ensure correct data returns, validating endpoint functionality, and load testing with specific scenarios using production data.
ReadyAPI supports API testing throughout the digital transformation process from prototyping to deployment. It is also used for API test automation and integration with Jenkins. Moreover, it assists in importing and structuring web services, API mockups, functional testing, security testing, deploying code to the cloud using containers, and integrating with third-party tools like Bamboo. With its comprehensive features for SOAP and REST service testing, ReadyAPI is recommended for a wide range of API testing needs.
Swagger Integration: Many users have praised the ability of SoapUI and ReadyApi to read in endpoints for a restful web service via a Swagger page or definitions file. This feature has been described as extremely helpful, with reviewers appreciating the time-saving aspect of not having to figure things out directly or rely on specs to build their requests. Additionally, the ability to easily update endpoints when they change was seen as a valuable feature.
Groovy Functions: Users have found the addition of groovy functions in SoapUI and ReadyApi to be very useful. They appreciate being able to use a programming language with Java libraries, which provides them with much more flexibility in how they process results and build follow-up requests.
Auto-generation of Test Cases: The auto-generation of test cases in SoapUI Pro has received high praise from users. It gives them a good head start on their testing efforts by building a set of tests that cover at least the happy path scenarios. Users also appreciate the visual guide provided by the test case GUI, which helps them structure their suites and scenarios effectively.
Cons:
- Lacking User Interface and Experience: Some users have found SoapUI's user interface to be confusing, old-fashioned, and not user-friendly. They have expressed the need for enhancements in terms of design and usability.
- Slow Performance: Several users have experienced slow performance with SoapUI, particularly when loading projects, switching between tabs, and during startup. They have also encountered errors related to insufficient memory, resulting in frustration and delays.
- Limited JMS Support and Third-Party Tools Dependency: Users have mentioned that SoapUI relies on an outdated 3rd party program called HermesJMS for JMS interactions. This limitation restricts their ability to run parallel test suites efficiently. Additionally, they have pointed out the limited support for JMS and the need for third-party tools for AMF method discovery.
Attribute Ratings
Reviews
(1-1 of 1)Companies can't remove reviews or game the system. Here's why
October 16, 2015
SoapUI despite the name is not a slipery tool that one always has problems grasping. In fact, it's the opposite!!
Score 9 out of 10
Vetted Review
Verified User
As a major hosting and Cloud company, we have thousands upon thousand of API that make calls across several programs, usually in very complex variations that involves coordinating not only testing back end of applications and API calls, but how they work and integrate with one another as we simulate a live production environment
So, SoapUI, after examining several different tools was the best candidate with all the modules and feature we needed to complete our testing. We did take a few steps further, due to the amount of tests that needed to run concurrently most of the time. But at the end, we managed to get maximum coverage of testing with a high degree of accuracy as we put in place redundant validation points.
So, SoapUI, after examining several different tools was the best candidate with all the modules and feature we needed to complete our testing. We did take a few steps further, due to the amount of tests that needed to run concurrently most of the time. But at the end, we managed to get maximum coverage of testing with a high degree of accuracy as we put in place redundant validation points.
- Ability to combine multiple test and adhere to the sequence that they need to run in order to complete successfully, regardless of pass or fail, the result is accurate.
- Excellent GUI design to make it as organic for the tester as they are revising or updating their tests. Once you get comfortable with the core functionality of SoapUI, you can explore the many added capabilities it has, like utilizing groovy or JavaScript. You can provide input and output files for the tests to use in sequence or randomly.
- Excellent reporting mechanism and options to print or to save to file. Also you can include verbose debugging content or create a shorter executive summary version. We even went as far as importing it to SQL database for cataloging and archiving for the sake of better tractability.
- Memory consumption, in large concurrent testing has been a challenge for SoapUI, mostly due to the amount of information that is getting written to the database, but there are workarounds to custom install SoapUI which for example runs on a Cloud server, where it can provide SoapUI the elasticity that it may need with large concurrent tests that run for while before completing.
- compatibility with all other databases and Open Cloud environment such as OpenStack out there in Open source, which I think is already in works.
- Integration of LoadUI is good, but to take serious step to compete with other performance and load testing tools
- On time completion of testing always translates and effects the ROI
- Accuracy and ability to meet the test coverage % that was planned also effect the confidence of the stakeholders
- Testers ramp up using SoapUI, therefore continue to become more and more efficient.
HP Products, Silk, IBM Rational suite of testing tools.
They just seemed to be overkill or mostly under the needed features. Some have made way to complex, where SoapUI manage to continue to improve the tool, but maintain the ease of use.
They just seemed to be overkill or mostly under the needed features. Some have made way to complex, where SoapUI manage to continue to improve the tool, but maintain the ease of use.
75
Various business functions related to internal and external critical applications and their accurate testing results. It's usage grew consistently over the life of the projects life cycle, which is my assumption, as I did not survey everyone in the group, that it indicates achieving desired results and upheld expectations from the tool used.
75
I would imagine this number would remain the the same or grow gradually, as to date, it had been the most effective testing tool considering the special needs of the project, and the application.
- API Calls clustered to test each one, as well as put a strain on the application and database to find the thresholds of it's load capabilities.
- Creating a nightly regression testing routine that would take several hours to complete.
- Tap into the raw data SoapUI generated, aside from standard reporting to find weaknesses, and potential risk areas.
- Using the data via linking it to an external database for a deeper look, and establishing better tractability.
- TBD
Yes
In the past HP Service Test, JMeter and other similar tools were tried, however to get the complete capabilities needed, the decision was simple. We had to choose the tool that worked with multiple platforms, various languages and databases. It is true that the best testing tool for any system depends on the make up of the system, but SoapUI covered a wider range, and our intention was always to minimize the number different tools that was being used for testing.
- Product Features
- Product Usability
- Product Reputation
- Prior Experience with the Product
If you have been in the field of testing for 10+ years, and work with test automation, you may be familiar with evolution of the testing tools out there. SoapUI for example due to having a Open source version rapidly evolved in features and improvements in usability, and establish a reputation among those who has used it before.
I think a very thorough evaluation of the development, build and deployment, and testing tool is just good practice. Specially if it is a brand new product you have started to build. It eliminates the possibility of having to go back and revise your plan, if you have done the due diligent properly.
Yes
Some clues and indicators of why the high memory usage climbing. Yes, it was addressed and eventually improved.
long conference calls with support engineer to resolve the memory issue bogging down the test machines, and kept at it until a workaround was in place and a hot-fix patch was applied.
- REST Calls, API calls
- Simulating live use by combining various calls that were dependent on one another, or another external return response to the call.
Yes, but I don't use it