We run around 10,000 different validations, including database validations, and we can complete the entire aggregation in less than one hour. This includes file validations, database validations, and response validations. All 10,000 plus the test conditions include all these three types of validations.

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.

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.

The solution saves us a ginormous amount of time. We used to write our own solutions, from small scripts to task web services, so this saves us thousands of hours.

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

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. 

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

It did help us to achieve timely testing of our APIs and the right reasons to enhance their functionality or performance.

We test services with SoapUI almost exclusively.

It save us a lot of time that before was wasted in manual testing. For example, we used to test OData Protocol queries, so we needed to compare the XML in the HTTP response with the data retrieved in the database. As it was a lot of information, each tester needed to pay attention to all this data in both places. With Soap UI NG Pro, this comparison just took a few seconds. That was really amazing.

It has helped us by integrating the tests in the nightly build format. Thus, the tests are performed automatically in each new software version.

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

Used for backend functional testing.

The tests are running fast and often which means that we get feedback about the tests very quick and then are able to evaluate the test results.

It helped us to make API mockups much faster, in addition to the functional and regression testing.

It helps me in speeding up testing process as all requests are saved and can be retrieved from a single location.

It's sped up testing as we move towards a TDD environment.

Testing web services manually, speeds up things.