What is most valuable?
How has it helped my organization?
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).
What needs improvement?
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.
For how long have I used the solution?
I have used this solution for twoyears.
What do I think about the stability of the solution?
I have not really encountered any issues with stability.
What do I think about the scalability of the solution?
The product is adequately scalable. It can handle composite test projects that contain many hundreds of tests.
How are customer service and technical support?
I would rate technical support as eight out of 10.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
The initial setup needs an automated headless installer.
What's my experience with pricing, setup cost, and licensing?
The license cost is a good value, but others not familiar with the tool are often skeptical.
Which other solutions did I evaluate?
We did not evaluate other options. We tried SoapUI first and its REST Discovery feature convinced us to adopt it.
What other advice do I have?
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.