08 May 2007 - 1.7.1 home user-guide eclipse jbossws intellij netbeans maven 1.X/2.X PDF files forums bugs sourceforge






Vote for soapUI at the WSJ Readers' Choice awards in the

'Best Web Services Utility' and

'Best Web Services Testing Tool'

categories

LoadTest Assertions

soapUI allows the creation of an arbitrary number of LoadTest Assertions for a LoadTest either from the LoadTest Statistics Popup Menu or from the "LoadTest Assertions" tab at the bottom of the LoadTest editor:

The toolbar at the top of the tab contains the following actions (left-to-right):

  • Add Assertion - prompts to add and configure a new LoadTest Assertion
  • Remove Assertion - prompts to remove the currently selected assertion
  • Assertion Options - shows the options for the currently selected assertion

Below the toolbar a table containing the configuration assertions is shown with the following columns:

  • Name : the configured name of the assertion
  • Step : the target step for the assertion
  • Details : detailed information on the assertion

A popup menu containing the same actions as in the toolbar is also available.

soapUI currently provides the following assertion types:

TypeShort Description
Step MaximumAsserts a steps max time
Step StatusAsserts a steps status
Step TPSAsserts a steps TPS
Max ErrorsAsserts the total number of errors
Step AverageAsserts a steps average

Step Maximum Assertion

The Step Maximum assertion checks that a steps max-time does not exceed a specified value. It has the following settings:
  • Name - the name of the assertion
  • Minimum Requests - the minimum number of runs that must have been executed before applying this assertion. Use this for avoiding assertion errors during startup of a LoadTest
  • Max Time - the maximum allowed step time. If this time is exceeded, an assertion error is logged to the LoadTest log
  • Max Errors - the maximum number of errors to allow before cancelling the LoadTest
  • TestStep - the target step to assert. Selecting "- Any -" will assert all steps, selecting "- Total -" will assert the total time taken for the entire TestCase run

Step Status Assertion

The Step Status Assertion checks that a step has not failed with an error, for example a Request steps or a Groovy script step. It has the following settings:
  • Name - the name of the assertion
  • Minimum Requests - the minimum number of runs that must have been executed before applying this assertion. Use this for avoiding assertion errors during start up of a LoadTest
  • Max Errors - the maximum number of errors to allow before cancelling the LoadTest
  • TestStep - the target step to assert. Selecting "- Any -" will assert all steps

Step TPS Assertion

The Step TPS Assertion checks that a steps TPS does not go below a specified value. It has the following settings:
  • Name - the name of the assertion
  • Minimum Requests - the minimum number of runs that must have been executed before applying this assertion. Use this for avoiding assertion errors during start up of a LoadTest
  • Minimum TPS - the minimum required TPS. If the actual TPS is lower, an assertion error is logged to the LoadTest log
  • Max Errors - the maximum number of errors to allow before cancelling the LoadTest
  • TestStep - the target step to assert. Selecting "- Any -" will assert all steps, selecting "- Total -" will assert the total TPS for the entire TestCase run

Max Errors Assertion

The Max Errors Assertion checks that the total number of errors for a specified TestStep does not exceed a specified value. It has the following settings:
  • Name - the name of the assertion
  • Max Absolute Errors - the absolute maximum allowed number of errors for the specified TestStep
  • Max Relative Errors - the relative maximum allowed number of errors for the specified TestStep, for example 0.2 will assert that at most 20% of the runs for the specified TestStep result in an error
  • TestStep - the target step to assert. Selecting "- Any -" will assert all steps, selecting "- Total -" will assert the total number of errors for the entire TestCase run

Step Average Assertion

The Step Average Assertion checks that a steps average does not go over a specified value. It has the following settings:
  • Name - the name of the assertion
  • Minmum Requests - the minimum number of runs that must have been executed before applying this assertion. Use this for avoiding assertion errors during start up of a LoadTest
  • Max Average - the maximum allowed average. If the actual average is higher, an assertion error is logged to the LoadTest log
  • Max Errors - the maximum number of errors to allow before cancelling the LoadTest
  • Sample Interval - the sample interval
  • TestStep - the target step to assert. Selecting "- Any -" will assert all steps, selecting "- Total -" will assert the total average for the entire TestCase run


Next: LoadTest Diagrams