TrustRadius Insights for ReadyAPI are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
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.
ReadyAPI is my go to tool. We do a lot of API testing, and with ReadyAPI the tests are easy to create and manage. The business problems we are able to address using ReadyAPI in conjunction with our CI/CD we can easily verify if a breakage occurs. When our tests start failing, we can easily trace back what the problem is connected to and easily verify whether the data returning is correct or not.
Pros
Test Suite Management
Test Step Updates
Import APIs from swaggerhub
Cons
Would love to see some built in groovy scripts for easy addition and editing
The documentation can be lacking, ex: Wildcards and how to implement, as well as groovy scripts
Love the dark theme, but wish I could pick colors, as some of the functions are hard to read
Likelihood to Recommend
As stated, we do a LOT of API testing, the swaggerhub import makes it easy to add APIs. This is very well-suited, as well as easy management of the steps/cases/suites inside of ReadyAPI. The one thing I do wish ReadyAPI was better suited for is changes to data, we have a lot of test cases in ReadyAPI and if we make a change to how the backend data is structured, one-by-one adjustments need to be made to the steps. Less appropriate, UI testing.
Alternatives
I have not used any other API tools, (new to QA) and the company already had ReadyAPI in place when I started.
Phase Change is in active development with our AI product, Cobol Colleague. We use ReadyAPI to validate API responses continuously using our CI/CD pipeline, which integrates with Jenkins and Test Rail. We also use the LoadUI Pro capabilities to do quick load testing when necessary, re-using our ReadyAPI (SoapUI Pro) tests. This re-use capability was a large reason we went with ReadyAPI.
Pros
Easy to use JSON path exploration to find the correct element to assert
Easy to re-use SOAPUI Pro tests in the LOADUI feature
Easy to integrate with Jenkins
Cons
Would be very handy to have some "canned" groovy scripts for more complex assertions - we had to create our own
API coverage reports just don't seem to make sense
Likelihood to Recommend
ReadyAPI is well suited for API assertion testing and lends itself to easily modularizing the functions being asserted. The integrations with Jenkins and TestRail are very easy to use. There is some flexibility in the scenario set up for LOADUI that we like - it's not as robust as some others (e.g. LoadRunner) but it does the job for us.
Alternatives
Postman and SwaggerHub
Postman didn't have the flexibility of detailed assertions that we needed, although it was easy to use. Also their integration points weren't as straightforward.
We use ReadyAPI for API manual testing and automating API tests. Developer team and QA team use ReadyAPI intensively.
Pros
Working with multiple scripting languages, firstly groovy
So handy for API mocking
It is easy to automate API tests
Cons
Usability can be improved. Sometimes doing simple something can be more complex
There are some performance problems. It uses more resources on computer.
Likelihood to Recommend
It is so simple to virtualise/mock API responses and automate manual tests. For example, when I need to mock some parts of API, I always prefer ReadyAPI.
Alternatives
Postman
Automating test cases is not functional in Postman, but in ReadyAPI you can do everything, even keyword driven development.
I use ReadyAPI [(formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro)] to quickly test web services. We consume services from many different vendors, clients, and other business partners. SOAP web services can be very tedious to manually test. ReadyAPI allows us to quickly import service definitions and test requests and uses cases before beginning proper implementation in our projects.
Pros
Import service definitions for quick discovery
Send requests and inspect responses
Set up test suites/cases
Cons
Code generation is out dated
XML generation can be a bit disorganized at times
Likelihood to Recommend
We use ReadyAPI [(formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro)] to test other web services for evaluation and discovery purposes. WSDL and other SOAP services are especially tedious to manually test in other generic HTTP testing tools, especially with large payloads. ReadyAPI lets us skip the needless scaffolding and send requests quickly, so that we can begin development on consuming the services in our projects.
ReadyAPI also allows configurable test cases for WSDLs, which enable integration testing of a service that might otherwise be difficult or tedious.
ReadyAPI can test REST and other simple HTTP requests, but is tedious for one-off testing of these types of APIs.
Alternatives
Postman
ReadyAPI vs Postman: ReadyAPI makes testing WSDL, SOAP, etc. much easier and quicker. Postman would require you to manually construct the SOAP envelopes and metadata XML, which is a lot of work for something that is meant to be a quick test.
Used by QA department to create automation tests for internal APIs, to interact with different compute resource providers like Kubernetes, AWS, vCenter, [etc.]
Pros
Easy to import swagger API definition
Easy to clone and modify existing test cases
Ability to check formatted API response
Cons
XML format is hardly readable
Properties are stored as strings only
Groovy console has small amount of prompts
Likelihood to Recommend
Pros: Create API tests quickly, even for inexperienced users. Import swagger definition which in turn allows all needed APIs to be covered.
Cons: Reviews are complicated due to xml format, lack of advanced scripting
VU
Verified User
Employee in Quality Assurance (Computer Software company, 201-500 employees)
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.
Pros
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.
Cons
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.
Likelihood to Recommend
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.
Alternatives
Postman
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.
VU
Verified User
Consultant in Professional Services (Computer Software company, 201-500 employees)
It is being used from time to time for testing our web services. I help developers to find and rectify issues, if any, before implementing it on the development system. It clears doubts about the functionality and output of the web service call.
Pros
Can be easily used by technical and non-technical staff in multiple environments that are familiar to them.
Its data-driven testing capabilities and real-world condition testing save a lot more time that can be put to some other usage.
It simplifies regression testing and clearly shows the test approach used and testing areas covered.
Test results and functionality can be tracked easily using test history and result comparison.
Its report building template is very cool and understandable they provide and highlights each and every required information in a better way.
Cons
It is quite heavy for old systems - The lite version could be beneficial for such old machines.
Likelihood to Recommend
SoapUI Pro is well suited when there is lack of testing staff or when your company needs through regression testing on a regular basis. It helps to use time efficiently and provide accurate results with lesser usage of manpower. It gives a brief idea about the output of your web services before actual implementation into your system.
Alternatives
Postman
It is robust and automated. It is a club of all the tools that are quite useful in every phase of the development life cycle.
VU
Verified User
Employee in Research & Development (Computer Software company, 501-1000 employees)
I am a technical product manager. While we are dealing with opening new services via our product, it becomes very vital to test the input and output of services to look for all possible values. It is used by all system/business analysts and product managers across the whole organization. It seems there is no better alternative because it is a compact tool and makes analysts' and product managers' lives easier while dealing with the whole functionality of our products.
Pros
Easy to see all possible methods of a web service, easy to create many different possible requests.
The formatted view makes it easy to see the whole request and response.
It's easy to share via colleagues including all possible trials.
Cons
Some features could be added via add ons like an HTTP monitor, test runner, some artifacts. With them, it becomes a big installation (modularity).
Sometimes it takes some time to open the interface; it is important to have a faster interface in today's applications.
It could include input and output beautifiers - this would make users happy because they may use this feature heavily while they are making documentation.
Likelihood to Recommend
For integration between two different systems, it is well-suited to show what parameters the client system should send and receive. In order to format output, SoapUI is less appropriate, and it is required to use other formatting tools.
Alternatives
I have used the "Advanced Rest Client." It has a faster interface but it is not as complete a solution as SoapUI in terms of structure and usage. If someone thinks professionally about integration projects, SoapUI is an essential tool that should never be missed.
VU
Verified User
Engineer in Information Technology (Telecommunications company, 5001-10,000 employees)