What is our primary use case?
Currently, I'm using this solution to test the API email applications
Usually, our clients are in IT. They have web services - more than 300 web services. We are calling those web services in our front-end applications. In order to verify the actual values from the web service, we use SoapUI to connect with the current client endpoint.
What is most valuable?
We like that we can do all manual testing for the API.
We can test as many APIs as we like.
It's very reliable and very easy to understand. Anyone can learn it very quickly.
The solution does not have major complications, it's a very simple tool. We can run projects in testing environments, and in production with the production data.
You can do end-to-end testing. You can also do security testing. You can create API projects. It's great in terms of usability.
The license for SoapUI is far better than Postman if you compare the two.
The initial setup is very easy.
The solution scales well.
What needs improvement?
It is helpful for individuals, however for a big team, for example, if I change any code in my project, for my colleague, it's difficult for them to use the same. This is the drawback. It's not ideal for teams and works best for individuals. If someone makes edits, it needs to be shared.
We would like it to be possible to share code in order to effectively work together.
Occasionally, when you are saving, the solution can hang. You might have to close it down and start again.
For how long have I used the solution?
We've used the solution for the last four years.
Buyer's Guide
ReadyAPI Test
October 2024
Learn what your peers think about ReadyAPI Test. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is very stable and very reliable. The performance is good. There are no bugs or glitches. it doesn't crash or freeze.
At the startup, when you open SoapUI, it takes some time to open. It takes some time to load all the files. There can be some lagging. Apart from that, every time you have to save your project, it can hang.
What do I think about the scalability of the solution?
The solution is easy to expand. It's scalable.
Around 25 people are using this SoapUI currently, however, mostly, 15 people are using the licensed version and ten people are using the free version. The licensed version is far better. You have so many extra features.
We do plan to increase usage.
How are customer service and support?
There is SmartBear technical support. They are very helpful. If we run into some difficulties, we ask them for help. For example, just three months before, we had some issues with the load testing. We didn't have the tech people here. We asked the SmartBear team to provide us with some people for the SoapUI load test. They provided us with an explanation about the load testing, and how it works in SoapUI and we were able to do it.
Which solution did I use previously and why did I switch?
We use ReadyAPI and SoapUI. Both products are similar, however, I'm not sure about the pricing.
How was the initial setup?
The initial setup is not complex. It's very easy. You just need the endpoint, and you add the project, if you want REST API, if you want XML, whatever, you can just add those from the file system. It's very simple. It's very easy for anyone. The entire setup only takes about one hour.
You only need one person to handle the deployment and maintenance.
What was our ROI?
We have seen an ROI, however, I can't speak to the exact numbers. We've had good results over the last five years, which is why we recently renewed the license.
What's my experience with pricing, setup cost, and licensing?
The solution does have a free and licensed version. We use both versions. The licensed version, however, does have more features and options.
We have 15 licenses right now and will likely increase them in the future.
My understanding is that the pricing is okay, however, that's taken care of by our procurement team. It's around $5,000 for three years. We extended just last month.
There aren't any costs beyond the standard licensing.
What other advice do I have?
This solution is stored on the database.
For individuals, this solution is great. For teams that would like to collaborate, it's likely not an ideal option.
I'd rate the solution at a nine out of ten. We've been very happy with its capabilities.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.