Web Service Testing with soapUI Part 4 – A Few Tips

I’ve found soapUI a valuable tool when working with web services. I previously wrote about how to get started and some test case basics here, here and here. I just want to add a few more tips I that took me a little bit of trying and reading to figure out:

Web Service Bindings

• Change or update the wsdl for a binding by right-clicking on it and selecting “Update Binding”.
• Double-click on the binding to open its properties. Here you can add more endpoints (urls pointing to other instances of the same web service) and assign them to requests. This is useful if we for example wanted to build the test suite against our development instance but then run the actual load test against a special test setup. In this window, you also can test your service for WSI-compliance.
• Add another binding by right-clicking the project and selecting “Add WSDL”.
• When having troubles with the WSDL import (especially if complex types are used by the service), try saving the wsdl to the file system and pointing the “Add WSDL” dialog to the file rather than using the “?wsdl” option on the live web service. The bindings endpoints may have to be updated afterwards (see above).

Load Tests
Once you have Test Suites like I’ve shown in the previous examples, you can use them to run load tests. Simply add a Load Test to the Test Suite via the context menu. This will open the Load Test screen where you can start your load test immediately.

Finally: For more details and ideas, look at the soapUI documentation at http://www.soapui.org/userguide/index.html.

Anke

Web Services

Written by: Anke Doerfel-Parker |