SoapUI: Project Walkthrough

Create a SOAPUI project from WSDL

Go to Projects in the tree
And select New soapUI Project

Give the project a name, then click ‘Browse’ and select the appropriate WSDL file.
Some WSDLs reference an XSD file that provides definitions to the data in the WSDL contract.

SOAPUI will create a ‘PortBinding’ branch on the tree with all the requests in the WSDL contract

Create and Use a Mock Service

A MockService will be created that contains all the responses in the WSDL contract/PortBinding
It will create a service on the 8088 port by default. This can be changed if needed.

Provide a name for the MockService, it is advised to keep the name short so it is easily recognized in the program

MockService is created but must be started to provide responses

The hour glass will move indicating the service is running

Next assign the PortBinding request to the MockService instead of the URL in the WSDL contract

Run the request and a response should be sent from the MockService

Editing a MockService Response

Open a Response under the MockService

Update the fields

Go to the applicable Request [StartInteraction]

Make sure to point the request to the MockService endpoint!!!

Run the request to see the updated Response data

Create Test Suite

Go to the PortBinding branch in the tree and select Generate TestSuite

While we really don’t need to create empty requests, leave them checked for learning purposes

Give it a name

The test suite will be created and added to the project tree

Open the TestSuite and each test case will be listed

Create a Test Case

Go to the Test Suite in the tree and select New Test Case

The Test Case will be created

Add Test Step

Add a Test Step. Test Request is a SOAP request.

A confirmation window will appear with 3 Assertions included. Leave Assertions check ( but you can add them later also)

The new Test Step will be added to the tree

Open the Test Step editor

Select Add for ‘requestDetails’ and ‘transactionTokenDetails’

Now you will see all the field in the request

Change the URL to point to the Mock Service and run the Test Step to get a response

You can see an Assertion Failed, making the SOAP icon red

At the bottom of the Test Case form, we can see the ‘Schema Compliance – FAILED’
At this point just disable the Assertion so the test will execute successfully.
Tweaking Assertions should be done once the Test Case is fully setup

Run the test step again and SUCCESS!!

Open the Test Case editor

The new Test Step is now present with green icon

Run the Test Case and the status at the top should be GREEN with FINISHED

At this point, just add more test steps to complete the Test Case….

Set Test Case Endpoint ( For ALL Test Steps )

While each test Step can be directed to a separate URL, it is best practice to set it one time at the Test Case level.

Reviewing Test Case Requests and Responses

Run a Test Case to generate a Test Case Log

Click on one of the executed Test Steps [GetToken] to bring up the Message Viewer

Message Viewer – Request Message

Message Viewer – Response Message

Message Viewer - Properties

Set Credentials for Test Case URL

Properties List

${PropertiesList#TransactionToken}

Transfer Properties

Go to the MockService Responses in the tree

Open ‘StartInteraction ‘

Setup MockService Response for StartInteraction

We’ll set it to ABCD1234567..

Open the Test Case that has multiple Test Steps

Open Editor

Add the StartInteraction, requestDetails, InteractionID field

It now shows….

Put ‘?’ in the field or it will automatically disappear

Make sure the endpoint is set to the MockService and Run the request to get a response from the MockService
The Right Side will be empty until request is run ONCE and receives a response

Now that we have a response, we tell SOAPUI to transfer a field from the Response to the next request.
In this case we want to Transfer ‘InteractionId’ to GetToken request ‘InteractionID’ ( note the different cases of ‘Id’ and ‘ID’

SOAPUI will ask for more information; where to SEND the Transferred data
In this example, send to ‘InteractionID’

SOAPUI will ask for more information and/or confirm the setting before creating the Property Transfer
We’re sending it to the ‘GetToken’ Step/Request
It is going to the Request portion of the Step

Update the name to ‘Field’-‘RequestName’ so it can be easily identified

Now the ‘InteractionId-GetToken’ property transfer has been created and added to already existing transfers

The complete tab
SOAPUI uses XPATH to identify items within the XML Response AND the target XML Request ( GetToken )
For the example:

Run StartInteraction Request and get ‘InteractionId’
Transfer ‘InteractionId’ to GetToken Request [ InteractionID ] field

After running the Test Case, go to the GetToken Step and open it in the editor

You will see the newly transferred value

Goto MockService

Open Start Interation

Setup MockService Response for StartInteraction

Test Coverage: WSDL Contract

This feature is helpful, but may not be required
Each request is created from the WSDL contract and it is helpful to know how much of the contract is used in test case

Select Enable Coverage and run the Test Case again

SOAPUI Test Reports

Automatically prepare coverage reports

Test Case Report

J-Unit HTML Report

Launch TestRunner

TestRunner Logs

Running SoapUI TestRunner for [MCX-GMPP-v2.16a]

directory: T:\TestFramework\SoapUI-4.6.2\bin

command: cmd.exe /C testrunner.bat -sGMPP-Success -r -a -j -f\TestFramework\logs\soapui -I T:\TestFramework\soapui\mcx\MCX-GMPP-v2.16a.xml

SoapUI 4.6.2 TestCase Runner

Configuring log4j from [T:\TestFramework\SoapUI-4.6.2\bin\soapui-log4j.xml]

10:01:59,465 INFO [SoapUI] Adding [T:\TestFramework\SoapUI-4.6.2\bin\ext\jxl.jar] to extensions classpath

10:01:59,466 INFO [SoapUI] Adding [T:\TestFramework\SoapUI-4.6.2\bin\ext\poi-3.9-20121203.jar] to extensions classpath

10:01:59,467 INFO [SoapUI] Adding [T:\TestFramework\SoapUI-4.6.2\bin\ext\poi-ooxml-3.9-20121203.jar] to extensions classpath

10:01:59,468 INFO [SoapUI] Adding [T:\TestFramework\SoapUI-4.6.2\bin\ext\selenium-server-standalone-2.37.0.jar] to extensions classpath

10:01:59,468 INFO [SoapUI] Adding [T:\TestFramework\SoapUI-4.6.2\bin\ext\SoapUiMCXD1.jar] to extensions classpath

10:01:59,818 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\lroberts\soapui-settings.xml]

10:02:00,727 INFO [WsdlProject] Loaded project from [file:/T:/TestFramework/soapui/mcx/MCX-GMPP-v2.16a.xml]

10:02:01,836 INFO [SoapUITestCaseRunner] Running SoapUI tests in project [MCX-GMPP-v2.16a]

10:02:01,838 INFO [SoapUITestCaseRunner] Running TestSuite [GMPP-Success], runType = SEQUENTIAL

10:02:01,913 INFO [SoapUITestCaseRunner] Running SoapUI testcase [InitializeMFS]

10:02:01,913 INFO [SoapUITestCaseRunner] running step [Start XShell]

10:02:17,415 INFO [log] XShell Closed

XShell Closed

10:02:17,440 INFO [SoapUITestCaseRunner] running step [InitMFS]

10:02:22,162 INFO [log] Called: MFS_Cust_Suspend_Release

10:02:22,164 INFO [log] Called: Selenium.MFS_Login

TestRunner Completion Message

Once the TestRunner completes the Test, a message will show

TestRunner LogFile Example