ReadyAPI Test Reviews

SoapUI is uncomplicated and user-friendly. 

I would like more documentation, training, tutorials, etc. Also, I don't particularly appreciate that I have to save everything. It takes up a lot of space on my laptop, but I have to install the WSDL again If I don't save it. 

I've used SoapUI off and on for about three months.

The scalability is okay.

Setting up SoapUI is straightforward. I just downloaded it and started using it. That's the good thing about it. I don't have to go through all those things.

SoapUI is open-source.

I rate SoapUI seven out of 10.

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.

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.

We use it for testing SOAP protocol API. We also started with the REST API recently. We use it to manually test as well as to automate a few API calls.

SoapUI provides us better usability and better features. People from different domains can use it effectively.

It clearly makes it easy to test APIs based on the SOAP protocol. We are a logistics company, and we have lots of tracking calls coming in. We provide APIs for tracking services, and it makes sense for us to use SoapUI to test them thoroughly.

There are no bugs or glitches, but a few features available only in the Pro version could be made available in the open-source version. Some of the features do not necessarily need to be only available to Pro users. The data generator would be really useful for the open-source version users.

The Pro version can be expensive for some companies.

For automation commands, it should be able to do what SmartBear is doing with ReadyAPI. They could filter on few things and pass on few things to SoapUI. The user database of SoapUI is bigger than ReadyAPI software.

As far as scripting is concerned, there should be consistency. For example, to declare a namespace, different syntaxes are used. Such things should be made consistent across SoapUI.

It is reliable. It has been good so far. 

It is easy to scale. We have around 18 people who use it. We have developers, QA, and customer support. We also have an E-commerce manager.

It is used very extensively because our major APIs are tested and deployed using SoapUI. Our customer care members use it for their day-to-day functions. They mostly use the manual part of it, whereas we do the automation part of it, which has the scope to grow.

If we are facing issues with the tracking calls or any other APIs that we have, a few members are trained to provide customer support. So far, we haven't come across things where we got stuck. They are usually user errors and not software errors.

I contacted SoapUi's tech support only once almost three years ago. I had emailed their tech support, and they responded fairly quickly.

I do the testing. I do not take care of the deployment. In its deployment, two developers were involved. All three of us are also responsible for its maintenance.

It doesn't take too long. Once it is deployed, I need to check if it works as expected, and the behavior is what is expected in production. 

It adds to the productivity of developers and QAs. So, there is definitely a return.

The Pro version can be expensive for some companies. There are no costs in addition to the licensing fees.

I would definitely recommend it to others. It is super easy to master once you know what you need to do.

I would rate this solution a seven out of 10.

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.

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.

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. 

We've used the solution for the last four years. 

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. 

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.

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.

We use ReadyAPI and SoapUI. Both products are similar, however, I'm not sure about the pricing. 

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. 

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.

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.

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.

We primarily use the solution for automatic testing and API testing.

The solution is extremely flexible.

The API speed is quite good.

The solution offers excellent integration capabilities.

Stability has been an issue for us. It needs to be looked at and made a bit better.

The load testing performance needs to be adjusted. It could work much more effectively, in my opinion.

They should work on the pricing of the solution. Right now, we find it to be overly expensive.

I've been using the solution for five years at this point.

The stability isn't actually that great, especially in relation to libraries.

We've been satisfied with the scalability. It's able to expand if we need it to. We're considering increasing our usage as well, so we're looking forward to its capabilities in that respect.

The technical support that we get with the solution is quite good. We've been satisfied with it so far.

The pricing of the solution is quite high. Those who want to use the solution should just be aware that it does come with a bigger price tag.

We're just a customer. We don't have a special relationship with the company in any way.

The solution is quite good. I'd rate it overall an eight on a scale of ten.

I'd recommended it. One of the main things that's great is the excellent integration into the DevOps tool-chain and the reuse of code between SoapUI and LoadUI. 

We were using this solution for unit testing.

The interface is user-friendly.

The documentation needs to be improved because the interface is not easy for a first-time user.

It would be better if the price of this solution was lowered.

We used SoapUI Pro for about two months. The last time we used it was six months ago.

We were in contact with technical support and they were useful. We are satisfied with the support.

I recommend this solution and my advice is to try it.

I would rate this solution a nine out of ten.

The primary use case of this solution is for API testing.

The most valuable features are that it is user-friendly, it's easy to use and easy to teach to others. Also, it has direct access support, which doesn't have any competition.

The automation needs improvement. We tried automation but it's not easy to integrate with the synching and some of the mission tools that we use for automated testing of APIs. That is the main section that we use and it needs to improve a lot.

They could include extra trial sessions with the extended license for critical types because they have trial versions that are provided for one month. For corporate companies, it is not enough time to explore and access it and give feedback on whether they are proceeding with it or not. They should include a trial session for at least three months. That would be very good.

In the next release, I would like integration with other tools to support software development, for example, Go! Zilla for defect management, so that I am able to test it, connect it, and trace it back to my requirement and log my defects seamlessly. 

I would like seamless connectivity with other software development tools.

We have been using this solution for a long time now, about four years.

This solution is very stable. We have not had any downtime whatsoever in the last few years that we have been using it.

Since we have been using SoapUI Pro, we have not required technical support because it is an easy-to-use tool. 

There is a lot of support online and it is quite simple and direct.

The initial setup was simple and straightforward. It took a short time to deploy.

The cost is not that bad.

I would recommend this solution. You should proceed and know that communication is very easy to use, and it's user-friendly. 

There is a lot of support online.

I would rate this solution a seven out of ten.

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.

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.