ReadyAPI Test Reviews

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. 

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 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.

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.

• 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.

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 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.