 |
The Message Content assertion has been superseded by the Smart Assertion as of ReadyAPI 3.9.0. The assertions will continue to be available, but we recommend transitioning to Smart Assertions. |
The Invalid HTTP Status Codes assertion checks whether the target test step received the HTTP result with a status code which is not on the list of defined codes.
This assertion works with test steps which receive HTTP messages.
Availability
This assertion is available in multiple ReadyAPI applications. Depending on the application, it validates the following data:
| In... | Checks... | To learn more... |
|---|---|---|
| Functional tests | The response HTTP status codes. | See Working With Assertions in Functional Tests. |
| Security tests | The response HTTP status codes. | See Security Assertions. |
Create an assertion
Follow these steps:
Click the image to enlarge it.
-
Open a test step.
-
Click Add assertion.
In the New Assertions dialog, search for the Invalid HTTP Status Codes assertion or select it manually in the Compliance, Status and Standards category.
Follow these steps:
Click the image to enlarge it.
-
Open a security test.
-
Click Response Assertion next to any scan.
-
Click
in the Assertions panel
In the New Assertions dialog, search for the Invalid HTTP Status Codes assertion or select it manually in the Compliance, Status and Standards category.
Setting up properties
Specify HTTP codes the target service should not return. To add multiple codes, separate them with a comma.
Example
To cancel the request when there is no content on the page, or it is partial, specify the following codes:
Other assertions for status codes and headers
Add more assertions for HTTP status codes and response headers:
See Also
Smart Assertion
Compliance, Status and Standards Assertions
HTTP Download Resources Assertion
HTTP Valid Status Codes Assertion