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.

We use to do end-to-end testing on mobile devices. Our team has about 50 members, but there are around 500 to 600 people in the whole organization.

SoapUI is very useful. Before we started using SoapUI, we had to do everything manually, which is very time-consuming, and there were a few things we couldn't validate. Using SoapUI made everything easier. You can do six to seven hours of work efficiently, and it's more flexible to use. Before, we had a manual Excel sheet folder where all the manual details were located. Let's say I am developing a particular part of it and it is assigned to some other company. Then we wouldn't be able to test it ourselves. Our client would lack confidence if we were doing manual testing. So that's the reason we used to have one or two teams. One would handle the development, and the other did the testing. But once we had been introduced to these automation tools, it was pretty much straightforward. With SoapUI, you can validate the test kits just by looking at the output screen. Now, we don't really need to have separate teams for development and testing. 

We can do all the automations at a nice pace in less time, so we don't need to spend two or three days testing. The times are changing fast with these new technologies and software solutions, so our relationships are fundamentally changed by these tools. In the future, we'll see more advanced versions of these tools, wherein everything will be done by automated processes. One day we'll be able to do complete tests in just five to 10 minutes.

One good feature is SoapUI's URL check, which allows you to check among the applications. I'm not just talking about the ones for Android. It has all kinds of multi-world tests that are really helpful.

In the beginning—I think it may have been the prior version—there was a lot of lag, but as the version updated, the lag decreased. SoapUI would also benefit from some more customization abilities. It's a good interface, but it would be nice if they added the ability to build custom dashboards where the user can do their own bar graphs and pie charts. It would be helpful from a management point of view. That way, the user can easily be able to know the status of the project. 

I have used SoapUI for the past year.

SoapUI is extremely stable, especially compared to the initial versions. The latest versions are very much stable. 

When it comes to scalability, SoapUI has some room for improvement right now. Its integration with iOS and Blackberry needs to be improved. They could add something like an Android signal that SoapUI is currently, which helps us do in-house development with a device.

We never called tech support at all. Mostly, took care of everything in-house. We only rarely experienced any issues. It's not the sort of thing that requires customer care all the time. 

Setting up SoapUI was relatively straightforward. Generally, we don't do the setups ourselves. The IT team takes care of the installation and provides the software to us in development. I believe it takes about 15 minutes, but I'm guessing, so I'm not very sure about that.

They have a partnership with my company. I believe it is essentially a year. They don't go monthly.

I would rate SoapUI nine out of 10. There are many solutions out there in the market, so it's not just SoapUI. But when we consider the SoapUI, it is far more stable. It is far more flexible and easy to use, especially if you consider other automation tools like Selenium IDE. Those are very standard tools wherein you won't get much flexibility. So always have to put in some time on other tools to get results, but in this case, it is more or less flexible, and the features are also getting pretty fast-paced. So yeah, it is beneficial, as the company's, I would say, every issue in the most we can get done. So yeah, it would be helpful for the developers as well as the testers.

We were using SoapUI to do UI automation.

Using SoapUI's automation suites to run all our test cases saved us a lot of time. Running 300 test cases takes about three to four days. When you automate all that, it takes only two to three hours.

We used SoapUI for Web API Automation as well as UI automation. With SoapUI's automation suites, we were able to make it very easy and readable by any other user. The test cases were written in a given format where we were able to fulfill the prerequisites by the given statement. We were able to very easily load the data into the database as a prerequisite for the UI and input the given steps using the GUI. 

And when we got to the part where we were performing the action in the UI, the integration between Selenium and SoapUI was very easy. In that step, it made it very easy to validate the UI. 

SoapUI is easy to learn. When we get a new tester on the teams, they can pick it up quickly.

SoapUI has a lot of features I like, such as the different data generators and data sources. The looping part of it is also good.

Grouping of the cases is not possible in SoapUI, to my knowledge. When working with critical cases or the, we were not able to group them properly. We can definitely create a suite and add them there, but within a whole suite, we have to identify them, which was not easy.

When we ran a batch of test cases, we were not able to initiate the next batch automatically. When one suite was completed, we had to trigger another the next test suite manually. That means something from one test suite to another. Suppose, there are 10 test cases in the first suite and another 10 in the second. We have to initiate the first 10 cases and then the second. When we were triggering from the project level, it failed to move from the first suite to the second, and I'm not sure why. But that was something maybe related to the code, not the tool.

I used SoapUI on one project in March 2021.

I was using ReadyAPI and SoapUI Pro. Sometimes it would get stuck, so we had to close ReadyAPI and then start it again. This would happen occasionally. 

And we were also integrating Humps JMS with the SoapUI for messaging purposes.  Sometimes it got stuck. We would have to end the task and then do it again.

It was on-premises. So whenever any tester needed it, they can set it up themself. 
It was not on the cloud, so I have not worked on the cloud. 

To activate the license, we had to use technical support from the SoapUI and that was very quick. They respond to emails very promptly. When you email them, they say they will respond in 24 hours, but it doesn't even take them that long.

The setup was a little bit complicated because we need to download the external JAR to support the Oracle database connection. We had to download the extra JAR for the SoapUI. We also had to do the Selenium setup. We need to create folders where we could place these — that Selenium standalone and the JAR. That was a little bit complex but not too bad. This was our first time, but if we had known what to do, then it would have been easy.

It was not straightforward because we had to integrate with Selenium and the external JAR was needed to set it up and automate the UI. But I was still able to do it by myself in two to three hours.

There was a big investment but the company definitely saw a return. The whole integration pack across the whole organization was using SoapUI. All the framework was designed only using SoapUI Pro. Each one of the testers had two licenses: one for the Windows machine and one for UNIX. But the organization definitely benefited because the releases were frequent and the automation was being done. 

I find SoapUI a little bit expensive because if I need to buy a personal license for one year, then it will cost around 700 to 800 pounds. I'm not sure what an enterprise license costs, but from an individual perspective, I found it costly.

So in my project, two tools were used: Postman and SoapUI Pro. In my organization, most use SoapUI Pro because it's easy to use. There are many more automation features actually in the Pro version of the SoapUI. I am not sure about Postman because we were using it a very basic level. I'm not sure whether automation is possible or not in Postman, but in SoapUI Pro it definitely is. 

I would rate SoapUI a seven out of 10. I would love to work on the SoapUI Pro again because it is really a great product. I would say definitely recommend SoapUI. It's a very useful tool and it will enhance your coding skills as well. It will help you learn to write code well. 
The framework is very easy. It's also easy to do functional testing, API testing, and virtualization. I would recommend this tool for anyone who has to do API testing or UI testing.

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.

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.

I use the tool for mocking, load testing, and developing. I use SoapUI Pro when the downstream is not available and we have to mock the downstream and continue our testing. I also use it to measure our application performance, etc.

I think their user-information sites should be better defined by SoapUI. For example, if I want to hit that virtualize server, let's say, with a 100K load — what is the bare minimum requirement? That kind of definition is not available anywhere. If that level of measurement could be given, that would be really helpful.

Tool-wise, I find no technical limitations as such. It's all as expected. It all depends on how much memory and how much you want to allocate. That's pretty typical for this type of solution.

I suppose the GUI could be slightly improved.

Right now, we don't have a way to capture the JVM stacks either for the virtualization or for the service when using SoapUI Pro for load testing.

I have been using SoapUI Pro for more than a year now.

Scalability-wise, it's okay. On a scale from one to five, scalability-wise, I would give SoapUI Pro a rating of four.

To be honest, I've never had to contact technical support; I just Goggle the answers to any issues I experience. I've never experienced an issue that required their assistance. It's a very simple solution to use.

If it could be sold as a bundle instead of by each individual component, that would be really great for the seller. It would be easy for us to understand what is included with the bundle.

I think the number of users is also limited, considering how much we pay. 

On a scale from one to ten, I would give SoapUI Pro a rating of eight. If the load and bare minimum could be defined, I would give this solution a higher rating. I don't expect a huge level of information, but at least a high level of information.

Overall, I think this solution is very cool and easy-to-use.

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.