ReadyAPI Test Reviews

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.

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.

• Data driving
• Easy to use

It has enabled a more thorough testing of our API layer.

There are a lot of bugs and it can sometimes be 'quirky.'

We have been using the solution for a year.

We had a stability issue but it is related to our machines only having 4 GB RAM.

We have not encountered any scalability issues.

The technical support is very good. Normally our issues are fixed within three months or if they are severe then by the next maintenance release.

I am not aware of any previous solutions.

Setup was easy. You just run the installer and set up your license.

The product is very good value but be prepared for some issues which you will have to work around.

We evaluated SoapUI, SOATest, UFT.

For the money this is a great tool.

There are many aspects of SoapUI NG Pro that have proved useful at all levels in our organization. From the automatic generation of example requests, to the Form view capabilities that allow for easy manipulation of a request for more basic testing. While the Testsuite capabilities of data driven testing, data generation, use of data sources/sinks, the various assertions that are easily setup automatic validation of your web services and finally the ability to link web services together to mimic your system test scenarios have really helped to improve our test quality and coverage while achieving that all important 'shift testing left'. 

With all of the capabilities the most valuable aspect of SoapUI NG Pro is that it is extremely flexible, you can add any amount of customization which can include the use of the substantial API that is available. With this flexibiltiy you can use this tool not only to test the functionality of the web service, or how that web service is implemented in your system but also to use the automated capabilities of this tool to test out the functionality of aspects of your systems such as calculation engines, letter generation, etc (this is specific to your system but can play a large part in your test strategy if considered) . 

We have used SoapUI Pro, now SoapUI NG pro for around 7 years and in that time we have made use of a lot of the capabilities of this tool. The main benefit this has given us in our organization is really in relation to how we plan our test strategy, it very much a combined effort between Architects, Development and QA. Everyone works towards 'shifting testing left' whether that is to provide mock services to allow for the step up of the test suite/test cases before the code/system is available to test or whether we plan to test our system before it is fully integrated. We very much work towards not only testing the functionality of the web service, or how it is implemented but also how we can use it to setup test data  or to test individual elements of our system before it is fully integrated. For us this has meant increased test coverage, better system security, less test execution time and above all a greater quality product. 

Better integration capabiliites with a range of Test Management Systems (not that it is not possible using the API) where a range of aspects are considered such as housing of the project, sharing (some capabilities here), versioning of projects, automatic saving of run information  and results (again this can be done in test suite setup but would be great to view in a test management system). There are some tools out there that do provide this but it would be ideal if this came as part of SoapUI NG Pro