Overall Satisfaction with SoapUI NG Pro
SoapUI is used primarily by developers looking to connect to and develop against our suite of enterprise services. It makes testing and discovery easy for them. Additionally, our services developers use SoapUI to test and support the services they write. Without having to write any code, the structure of services can be quickly examined, and specific use cases tested. When the code is not behaving as expected, running a quick request in SoapUI is often the fastest way to narrow down the source of the problem.
- Quickly and easily discover and connect to service endpoints
- Create and save test requests for easy re-use
- Immediate "is the service up and responding" checks.
- The UI is written in Java, and as such sometimes behaves in unexpected ways - ways that a native Windows UI would not.
- Startup time can often be painfully slow. Once the program is running, it performs well, but starting up can sometimes take nearly a full minute. I believe this is also due to having been written in Java.
- I used to consistently get errors about not having enough memory for the program to start up (in spite of having far more memory than it will ever need in my machine). I solved the problem by manually tweaking the startup script to allocate more memory to the Java Runtime Engine. However, this solution seems to have exacerbated the slow startup time I mentioned above.
- SoapUI has been an invaluable addition to our development and testing toolkit. If something like it did not exist, we would likely have tried to write something ourselves.