They are primarily used to either send or receive messages, which can then be validate via an standard assertion mechanism (described in Validating Messages). These are the main TestSteps for validating the functionality of your services. So, let's have a look at the different types of TestSteps available followed by a couple of example TestCases so you can get a feeling for what is possible! Sampler TestSteps The actions marked in green are specific for the selected TestStep, the others are common for all TestSteps. When selecting a TestStep, its right-click menu exposes corresponding actions and the bottom left properties table shows related properties that can be set, as for example shown below for a SOAP Request TestStep: Any number of TestSteps can be added to a TestCase add them by either right clicking in the TestStep list and selecting add/insert or by pressing the corresponding TestStep button in the TestCase window: TestSteps are by default executed sequentially, but several possibilities exist for branching, looping and even calling other TestCases, making complex testing possible when required. To try the new functionality, feel free to download a ReadyAPI trial.Īs mentioned previously, TestSteps are the core building blocks of functional tests in soapUI each TestStep performs some step for validating the functionality to be tested. Some of test steps in this article relate to standalone ReadyAPI that has been replaced with ReadyAPI.

Download steep target for free