18 November 2008 - 2.5 user guide blog eclipse intellij netbeans maven PDF files forums bugs sourceforge eviware.com


Eviware Logo

Test Requests

soapUI defines three types of Request Steps:

  1. SOAP Test Requests - calls a WSDL Operation defined in the project
  2. REST Test Requests - calls a REST REsource defined in the project
  3. HTTP Test Request - calls an arbitrary HTTP service

The first two of these are internally linked to and dependant on their corresponding operations/resource and therefore also indirectly dependant on their containing services, which they need for validation, request generation, etc. Removing the service will also remove the corresponding Test Requests (a future feature will be to convert them to HTTP Test Requests).

Common for all these is that they add an Assertion possibility for validating the response received from the target service.

The Assertions Tab

The Assertions tab lists the assertions that have been configured for the TestRequest. Double clicking an assertion in the list opens that assertions' configuration dialog (if available). Any number of assertions can be added, often it may be relevant to add the same type of assertion multiple times with different configurations.

A colored circle next to the assertion indicates the status of the assertion in regard to the last received response; red = assertion failed together with error messages, green = assertion ok, grey = assertion has not been performed.

Assertion Tab easy adding of assertion

The toolbar contains corresponding actions and a "Clone Assertions" action for cloning a number of assertions to other TestRequests (see below)

The following actions are available from the assertion lists right-button menu:

  • Add Assertion - prompts to add a new assertion to the list.
  • Configure (if possible) - opens the selected assertions' configuration dialog.
  • Clone (if possible) - prompts to clone the select assertion.
  • Rename - prompts to rename the selected assertion.
  • Remove - prompts to remove the selected assertion.

The Request Log Tab

The Request Log tab simply shows a history of submit/response times and response-sizes for the TestRequest. This can come in handy if you want to manually compare response times or sizes over time.

The Request Log Tab for Logging Web Service Tests

Request Result Viewer

When executing a Request Step from within a TestCase (or associated LoadTest) the actual request/result and associated properties for that request can be viewed by opening a "Request Result Viewer" either from the TestCase editors log list or from a LoadTest editors log by double-clicking the associated log entry. Sent or Received attachments are currently not saved to preserve memory.

The viewer shows 3 tabs:

  • Request Properties - shows request and reponse properties for the request
  • Request Message - shows the actual request message sent, including expanded properties, inline files and MTOM/XOP Includes..
  • Response Message - shows the response message received

Viewing a A Web Service response

Clone Assertions

For SOAP Requests, soapUI Pro contains a right-button or assertion toolbar action for cloning an arbitrary number of assertions to other TestRequests. The dialog shown is as follows:

Clone Assertions for Agile Web Service Testing

The options top-to-bottom are:

  • Assertions - select the assertions to be cloned
  • Target TestSteps - select the TestRequests to clone to
  • Target TestCase - the target TestCase
  • Target TestSuite - the target TestSuite
  • Target Project - the target Project
  • Overwrite - overwrites existing singular assertions (ie those assertions that can only exist once, for example SoapFault, SchemaCompliance, etc). If not selected and the corresponding assertions exist in the target TestStep(s), they will be ignored.
  • Open List - opens a separate window after the update containing a list of all Requests/TestRequests that have been modified during the clone procedure (useful for manual post processing).

Setting the desired options and selecting OK will clone as configured, alternatively use the "Apply" option to execute the current Dialog settings without closing it.


Next: SOAP Requests