Applies to Ready! API 2.0, last modified on May 16, 2017

Ready! API includes a large set of standard and specialized assertion types that you can customize to suit any combination of API calls. You can create assertions chains, various scenarios and automated workflows.

Organizing and Running Assertions

You can use assertions to validate the message the test step receives. Usually it compares some node of the request or response to value you expect to get.

Each test step can use multiple assertions, so you can validate various aspects and content parts of the request or response.

After the test step’s execution, Ready! API applies all its assertion to the request or response. If any assertion fails, the test step will appear as failed in the test case view. A corresponding FAILED entry will appear in the test execution log.

ReadyAPI: The failed assertion in the transaction log

Click the image to enlarge it.

Ready! API provides a complete solution for the verification process, allowing you to perform all the steps and testing them in the same time. This allows you to separate setup problems from execution, and derive operation results and stating issues. With this approach, you can easily perform the validation and find the problems’ origin.

Assertion Categories

There are several categories of assertions in Ready! API. During run, only assertions available to the specific test step will be enabled.

In the Recently category, there are 5 assertions you have used recently. Some of these assertions may also be disabled due to the source and property restrictions.

To learn more about specific categories and assertions, see Assertions Reference.

Managing Assertions

The Assertions panel similar in SoapUI NG, Secure and ServiceV.

The following screenshot depicts 3 assertions within a SOAP Request test step. The first two of them have passed correctly, and the last one have failed.

ReadyAPI: The Assertions panel

Click the image to enlarge it.

Adding Assertions

To add a new assertion, click .

The Add Assertion dialog appears.

ReadyAPI: The Add Assertion dialog

Click the image to enlarge it.

  1. Select an assertion category.

  2. Select a specific assertion.

  3. Click Add.

The assertion will appear in the list.

Configuring Assertions

To configure the assertion, click .

For different assertions, the available settings may vary. To learn more about the specific assertion settings, see Assertions Reference.

Removing Assertions

To remove the assertion, click .

Changing Assertions Order

To change the assertions’ order, use the arrow buttons.

The assertions order is important, since Ready! API runs them in order you have provided, from the topmost to bottom one.

Cloning Assertions

To clone the assertion, click .

The Clone Assertions dialog appears.

ReadyAPI: The Clone Assertions dialog

Click the image to enlarge it.

Here, the following options are available:

Option Description

A list of available assertions to clone.

Target Project

A project to clone the assertion to.

Target TestSuite

A test suite to clone the assertion to.

Target TestCase

A test case to clone the assertion to.

Target TestSteps

A list of available test steps to clone the assertion to.


Replaces any existing assertions with the same name.

Clear Existing

Removes any existing assertions with the same name.

Open List

Displays the list of updated test requests.

Specify the parameters you need, and click Apply to apply changes, or OK to apply changes and close the dialog.

See Also

Verifying Results
Assertion Reference
Assertion Coverage