Skip to main content
TrustRadius
ReadyAPI

ReadyAPI
Formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro

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…

Read more
Recent Reviews

TrustRadius Insights

SoapUI and its Pro version, ReadyAPI, are widely used tools for integrating, verifying, and testing web services. They are highly scalable …
Continue reading

ReadyAPI

7 out of 10
January 13, 2022
Incentivized
We currently develop an ERP accounting system that makes use of an API such that third-party systems can integrate with us. Ready API …
Continue reading

Speeding up QA tasks

9 out of 10
January 12, 2022
Incentivized
We use ReadyAPI almost daily for API testing and automating our test case suite for future runs. This helps us especially when doing …
Continue reading

ReadyAPI : Good Tool

9 out of 10
January 11, 2022
Incentivized
ReadyAPI enables our team to create, manage and run automated functional, security, and performance tests of RESTful, SOAP, Kafka, and …
Continue reading

To ReadyAPI or Not

9 out of 10
December 06, 2021
Incentivized
ReadyAPI is used to validate endpoint functionality and for load testing. The main purpose of using the tool is to create specific …
Continue reading
Read all 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

Return to navigation

Pricing

View all 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 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.

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.

Return to navigation

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
Return to navigation

Product Details

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 Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Postman, Parasoft Development Testing Solutions, and Jest are common alternatives for ReadyAPI.

Reviewers rate Usability highest, with a score of 9.9.

The most common users of ReadyAPI are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(155)

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!

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:

  1. 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.
  2. 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.
  3. 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-3 of 3)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
It is being extensively used for importing web services and also creating a structure for web services. As a QA Automation Engineer, I am using it for API mockups, functional testing and even load testing. The security test feature is really helpful in checking the SQL injection and malicious code attachment with just a few clicks. SoapUI is helping us to deploy the code to the cloud with the help of containers, as all this possible because of the robust integration of SoapUI with the other third-party tools like Bamboo.
  • By defining variables, you can customize parameter values without hard coding the values in the whole test-case.
  • You can also use external data sheets to retrieve data to your executions.
  • MockResponse module should be more enhanced and simplified.
  • I wish SoapUI would allow you to make a sample request which only consists of the required fields and leaves the optional fields out of the sample.
It will help you to create envelopes and headers to satisfy WS-Security, WS-Addressing, etc. IT has a wide range of assertion options. If you are still not satisfied, you can write your own assertion with the help of Groovy script and can use any Java library to do so. The Maven Support. You can simply export a TestSuite from SoapUI and run it from outside on your CI/CD tool (i.e. Jenkins, Gitlab, etc.) with the help of Maven.
  • The testing turn round time for a new web service has been decreased drastically and we can get the product out in the market in no time.
We selected SoapUI because it generates tests easily using drag and drop, and point-and-click. It gives powerful data-driven testing with data from files and databases. Scripts can be reused easily.
We had an extra option to integrate it directly with our build tool, Jenkins, and also monitor the ongoing traffic for the live environment.
10
ReadyAPI was used by multiple QA teams in the organization to create and run API scripts for the APIs being created. The APIs were being created for the fintech to be used, they contained a lot of business logic based on the different needs of the customers. The job of the QAs was to make sure that all of the functionalities are tested before the APIs are pushed to live
None
  • Test the APIs before pusing to Live
  • Integrate with Jenkins
  • Get results of all the scripts by running them overnight
  • Help learn new QAs get their feet wet with API testing
  • The drag and drop functionality is phenomenal
  • Point and click interface makes it easier to learn and build scripts
  • Swagger intergration helped the non technical team get a sense of the APIs
  • Better reporting tools using ReadyAPI
I would definitely renew the ReadyAPI as I was pretty happy while using it. But then I switched my job, and the current workplace is using Postman so we are using it for now. Plus, I don't have any issues with Postman. At the end of the day, it about selecting the tool that gets your work done more efficiently.
No
  • Price
  • Product Features
  • Product Reputation
  • Prior Experience with the Product
The Product features like helping with 100% code coverage, assisting in test script creation, integrating with CI/CD, fitting well into the agile environments, great user community were some of the important factors that led to the selection of the tool. Some members of the team had good prior experience with the tool, so they also recommended using the tool.

The overall pricing was also better than other tools present in the market, so that was another big factor
Looking at the current scenarios, I might change the evaluation scenarios because at present there are other tools providing similar or better functionality for API testing. We are currently using Postman in our ongoing project, which seems to be fitting well into our business model. The paid teams collaboration function is a great function to share the scripts across the team using the Postman cloud, and it comes with a lot of ad-ins to integrate directly with build tools like Jenkins.

But looking at ReadyAPI, the team was pretty satisfied with the tool and I don't have anything negative to say about it. Who knows, we might be using it in the next project
To be honest, we didnt had much issues with the support, as there is already plenty of online communities available for help. But if ever there were some minor issues with the membership or the certificates, the tech support was always quick and efficient enough to resolve the issue ASAP
No, we did not, as the team didn't feel the need for it. We had people with prior exp for ReadyAPI so we confident enough that we would not be requiring the premium support. Plus, there's plenty of resources available online to help the users, so those came in handy too
No
Not that I could think of. The service was always good though.
Christopher Saleh | TrustRadius Reviewer
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.
  • 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
Well, obviously if the technology and application back end is supported by SoapUI, which 98% of time, it is. However, there are new methods other than Rest, etc. are coming out that would require SoapUI to be compatible. Also, built in popular add-on such as AWS support can be expanded to support similar companies to Amazon.
  • 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.
It has been good throughout, but it has also improved in the recent years, which is a great indicator of value that is put on the need for solid support for customers. Any tool is basically as good as the support that stands behind it. Period.
SoapUI allows us to combine multiple tests and adhere to the sequence that they need to run in order to complete successfully. It has an excellent GUI design and the reporting mechanism is also very good. It does consume a lot of memory though during concurrent testing.
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
Invested in 1000 of hours reusable test script and modules, and it still seems to be growing. Not to mention that even without that consideration, it would still be the choice for the type of testing SoapUI provides. It is in investment that was wisely made, and requires us to stay the course.
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
It has an excellent GUI design and the reporting mechanism is also very good. It does consume a lot of memory though during concurrent testing. However, I have read that added monitoring tools have been added, which if so the 7 could possibly go to a 8 or 9.
Soap UI has managed to continuously build on it's solid foundation and keep improving by each release. It is by far the most dependable and accurate testing tool out there of its kind. Available via connecting to VM's created as SoapUI test machines give access to it anytime, anywhere practically.
It has an excellent GUI design and the reporting mechanism is also very good. It does consume a lot of memory though during concurrent testing.
Score 6 out of 10
Vetted Review
Verified User
SoapUI is used mainly in the QA departement to test web services i.e. REST and SOAP. I know it is being used in my departement and in other departement Solve test automation problem and performance testing. not very happy with the load test module
  • Records Rest requests, easy way to record them and make functional testing easy
  • Records Soap requests, , easy way to record them and make functional testing easy
  • Changing parameters on the requests
  • Assertion on responses easy too and user can save responses
  • Rest Mocking is very nice feature to start testing early and give early feedback
  • Sometimes it is not easy to maintain, work flow testing is not intuitive
  • Json assertion not very easy to do
  • Caching responses does not help getting accrate performance numbers
  • Security testing still something new
Easy to learn and to use. but sometimes buggy and they are not very responsive to fixing bugs. Also user community is not very big yet
  • Positive repeatable steps, easy to learn
  • Positive employees more efficent and effective
  • Negative not very good customer service from their side
  • Positive help us have more coverage -> more automation -> better quality
Compared with HP Service Test: selected SoapUI as it was way cheaper and easier to learn . Also, I always had bad customer service experience with HP so decided to a different route.
Previous experiance. I have not had to submit new tickets so I am not sure if it is getting better
needs better documentation
3
3 people use it in one of the R&D depatements
1
Does not need much support
  • functional testing
  • performance testing
  • test automation
  • we just use its out of the box functionality
  • thinking about trying loadui again
I need to evaluate again what I am getting for paid license versus the free version
No
  • Price
  • Product Features
  • Product Usability
  • Third-party Reviews
Product feature, we need most of the feature we use to be out of the box so we do not have to customize work flows and features
would love to find more websites like trustradius to collect user feedback
  • Implemented in-house
No
easy install
Change management was minimal
was not a big implentation project
  • Poor documentation
  • small user community
  • want better documentation about known issues and limitations
no very easy but lacks documentation
No
do not have the budget
Yes
no
Did not really have this experience yet
  • creating SOAP requests
  • creating Rest requests
  • Assertions
  • editing requests
  • creating test suits
  • load testing
  • workflow testing
Return to navigation