ReadyAPI Test Reviews

We are using SoapUI Pro as an API testing tool. We do API building, testing, and tracking.

SoapUI Pro could improve by having dashboards.

I have been using SoapUI Pro for approximately two years.

The stability of SoapUI Pro is good.

We have not had a problem with the scalability of SoapUI Pro.

We have approximately six people using this solution. We will increase usage in the future.

The Pro and free version of SoapUI Pro has good technical support.

The initial setup is straightforward and it takes less than 30 minutes.

We did the implementation in-house of SoapUI Pro. We have one person that is assigned to SoapUI Pro for maintenance and support.

SoapUI Pro is open source but it has a subscription-based model which involves some more features. At the moment we are using the free version. The Pro version requires a license, and it is an annual license to use it.

I would recommend this solution to others.

I rate SoapUI Pro an eight out of ten.

• Prepared different kinds of testSteps
• It's easy to add assertions in the Pro version
• Groovy scripting
• Event handlers

Used for backend functional testing.

• Improve bug fixing
• Stability
• Memory consumption
• Exclude test results out of projects (xml file)
• Improve composite project mode (tried version 1.2,1.3 but after short time refused)

I've used it for more than three years starting with SoapUI Pro version 4.6.x. SoapUI NG from beginning after renamed to Ready API and be part of it.

8/10 - the answer for reported bug was a known issue and a fix will be a part of future releases, no time scale given. The bugs are are in many releases.

I have not used other solutions for back and testing personally. Comparing to robot framework SoapUI had more pros than robot framework.

Initial set-up of program is straightforward, preparing own project with dynamic path e.g. JDBC connection or endpoint is more complex.

The product is a good solution for functional back end testing, but the price should be lower due to already mentioned problems, bugs. Use other product framework for small solutions, due to price/bugs. The advantage is that the product is handy for testers, user friendly; ability to use load, security tests or create mocks.

An automation tool not only always has the purpose of redefining the APIs after their functional or performance testing, but also provides an easier execution platform for the APIs so that they can be easily consumed by the future developers who are yet to work on them.

It did help us to achieve timely testing of our APIs and the right reasons to enhance their functionality or performance.

I've majorly worked on SoapUI Pro, LoadUI and Service Pro and found all of them equally useful and very easy to understand tools.

The tools that are stated by SmartBear speaks for itself, but when it comes to improvements, there could be a release which only aims for the development of beginners in terms of understanding the tools that are laid by SmartBear.

The most valuable feature is the ease of project and test suite set up. A few clicks and imports and your project is set up.

We test services with SoapUI almost exclusively.

I cannot attest to the Ready Pro version, as I'm not really a fan of that version even though I am sure it offers a lot. I downgraded from that version after I installed it. I liked the earlier versions for what I do in the tool.

It would be nice to have an easier way to determine operation in the test case itself.

I've used it since 2012.

There were no issues with the deployment.

It has met and handled everything I have had to test with ease.

It has met and handled everything I have had to test with ease.

Very high. Whenever I have had to use the website for assistance I have found the answer there without having to call in.

I have not used anything like this tool. Eclipse does a lot that I need but SoapUI does as well.

I don’t recall, but I do remember it was fairly simple. Install and add the license and I was good to go.

We did our implementation in-house.

I don’t recall, but I do remember it was fairly simple. Install and add the license and I was good to go.

Great tool. Makes API testing super easy to set up and use.

SoapUI Pro is a good tool when it comes to API design and orchestration. Additionally, it is beneficial for functional and for performance testing.

SoapUI Pro is a little heavy due to the number of features. Previously it was not that heavy. Now the tool is too heavy, they should work on fixing this issue because until your system has lots of resources, you won't be able to use it seamlessly. The performance of the application itself could improve.

I have used SoapUI Pro within the last 12 months.

SoapUI Pro is a stable solution.

The scalability of SoapUI Pro is good.

The technical support is very good. They are knowledgeable and responsive. I have contacted support multiple times. Whenever we had an issue with respect to some enhancement that we require we had a good experience. Some of the issues we had could be because of our lack of knowledge of the tool or the utility, however, they were quite helpful. The moment we sent a mail to support, without delay, they responded back. Whenever we interact with them, they will throw more light on how the way the solution can be explored or used better. Their team is good, they're always ahead of the race.

I rate the support from SoapUI Pro a four out of five.

The initial setup of SoapUI Pro 

The return on investment we have received is very good.

SoapUI has two versions, open-source, and commercial. You can use the commercial version or you can look for the open-source if you are trying to achieve basic steps out of the APIs. However, if you want to scale it up and want to integrate it with CI/CD seamlessly, then you should choose the commercial version.

I rate SoapUI Pro an eight out of ten.

The most valuable features are:

• Test validation on API responses.
• Mock services to test parts of the application.

Mock services are valuable as we can start testing the interaction of an application with another application without having the other application fully available. It might be the second application is not live yet. We substitute the second application with a mock service (a type of a stub).

It has helped us by integrating the tests in the nightly build format. Thus, the tests are performed automatically in each new software version.

The licenses could be more flexible with regards to floating licenses.

In the case that a user changes a workstation, then the license locked to a certain workstation cannot be easily changed to another workstation. It would be more flexible if a license could be linked with the user personally.

Compared to i.e., Telerik Test Studio, you have a license that is connected with your email and password. So if a user changes machine he can release the license on the old machine, go to the new machine, and hook in the license there with his email and password, and he is up and running again.

With SmartBear, you have to contact the company to tell them that you have changed machine, etc.

I have used this solution for five years.

There were no big stability issues, there were some issues in regards to the correct saving of projects. You should save often!

There were no scalability issues experienced.

I would give the technical support a seven out of 10 rating.

The setup was straightforward.

This product is quite useful for us. It could be even more useful if we had explored other functionalities (security, load tests) as well.

I found the REST Discovery and Groovy scripting features to be most valuable. Additionally, the Simple programming model enables a wide audience (in contrast to Java or JavaScript). The XML format makes it easy for scripts to analyze the test base (metrics, bulk simple changes).

Using this solution, we developed tests about three times faster than we did with Java and by doing manual REST reverse engineering from product code (Java). This solution also enabled manual testers to write automated tests, which they would not have been able to do in Java. We are planning to get SoapUI tests written earlier (thus moving some test development upstream).

Working with Git needs to be improved. SoapUI 1.8.0 has this annoying habit of touching/changing many files that are unrelated to a test developer's actual change. This habit complicates working with Git, since Git thinks that the user has made hundreds of changes.

I have used this solution for twoyears.

I have not really encountered any issues with stability.

The product is adequately scalable. It can handle composite test projects that contain many hundreds of tests.

I would rate technical support as eight out of 10.

I previously tested TestNG/Java. With this solution, we were able to develop tests about three times faster than we did with Java and by doing manual REST reverse engineering from product code (Java). This solution also enabled manual testers to write automated tests, which they would not have been able to do in Java.

The initial setup needs an automated headless installer.

The license cost is a good value, but others not familiar with the tool are often skeptical.

We did not evaluate other options. We tried SoapUI first and its REST Discovery feature convinced us to adopt it.

Evaluate this solution in a pilot project. Remember that, as test numbers grow, test maintenance will become an issue. Implement scripts to apply verification rules across the test XML files, to ensure that test authors are following team conventions. That will reduce the number of avoidable errors that usually get introduced into the test base.

Functional and load testing of the APIs we've developed internally and the APIs we've consumed from external parties.

It helped us to make API mockups much faster, in addition to the functional and regression testing.

API mockups, functional testing, and load testing. API mockups is a feature that quickly allowed us to have a working API mockup interface during the initial API discussion meetings.

The UI should be improved a little. 

It would be great to integrate the graphing module for load testing, so that we could analyze the timings of the responses and how that changes over time with changes in the API implementation logic.