This blog post focses on testing a soap web service provisioned by PO using a tool called SOAPUI. This is a free and open source cross-platform Functional Testing solution. With an easy-to-use graphical interface, and enterprise-class features, SoapUI allows you to create and execute tests. In a single test environment, SoapUI provides complete test coverage and supports all the standard protocols and technologies.

Installation

Requires a JAVA JRE

SOAPUI can be downloaded from http://www.soapui.org/


Creating a test

You will need a Web Service Definition (WSDL) to test with. You can export a web service definition from PO (ID) or Import the Web Service Definition supplied by your partner.

15-09-2015 16-15-10.jpg

Right click on the Workspace and select New SOAP UI Project (please use a meaningful name) and the browse for the WSDL you exported from PO.

15-09-2015 16-24-30.jpg

The web service will be imported and displayed in the top right hand window. Click on the plus sign next to the web service to expand it.

By default a request will be created for each operation of the web service. The requests will be called Request_1.

15-09-2015 16-17-23.jpg

It will use the operation definition to create a basic request and you will need to populate this request with the appropriate values. The username and password will need to be input for each request in the ‘Request Properties’. You shouldn’t have to change any of the other values.

For PO Web Services the endpoint will be the PO system you exported the Web Services from. This can be modified or new endpoints added.

  15-09-2015 16-18-37.jpg

You may need to configure a proxy server. This can be found under File, Preferences.

So once you have a service and have configured a request, entered your account details, updated the payload and the end point you are ready to run the test. Just click on the green arrow above the request to start the test.

The response will appear in the right hand window.

15-09-2015 16-19-17.jpg

The response time for the request will appear at the bottom of the screen.

15-09-2015 16-20-52.jpg

Clicking on HTTP log at the bottom of the screen will provide information about the request. This may be useful when investigating problems with the service.

15-09-2015 16-20-00.jpg

In my experience there are three main problems that can occur. Failure to enter the correct credentials, failure to enable or disable the proxy and finally, an incorrect endpoint. All these should be checked.

You have now created your first SOAP UI Test. If you wish to run another test for the same operation with a modified payload you can duplicate the test by right clicking on it and selecting Clone Request. Remember the endpoint and the username and password are defined for each test. So you will have to select the correct endpoint and enter your credentials.


Blogs in Series

Blog 1: HTTP Post Testing: Test Tools…Part 1 *HTTP *

Blog 2: SFTP Testing: Test Tools…Part 2 * SFTP *

Blog 3: REST  Testing: Test Tools…Part 3 * REST *

Blog 4: SOAP Testing: Test Tools…Part 4 * SOAP *

Blog 5: SOAP Testing: Test Tools…Part 5 * JMeter *


To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply