# Assertion

{% embed url="<https://youtu.be/lcBZg1DAtvw>" %}
Ddosify Assertion Feature
{% endembed %}

At default, Ddosify marks the step result as successful if it sends the request and receives the response without any network error happening. Status code, body type (or content), or other metrics does not have any effect on success/failure criteria. But this may not be a good test result for your use case and you may want to create your success/fail logic. That's where you can use Assertions.&#x20;

Using the no-code capabilities of the Ddosify Platform, you can easily create assertion logic based on various factors, such as status code, response time, response size, response body, response header, or captured variables. Additionally, you can combine multiple assertions to develop more intricate logic.

#### Create Assertion Logic

1. Click the ***More*** button located to the right of the step and open the "Step Details" section.

   <figure><img src="/files/rrd7SiSyNSfUILIth5hn" alt=""><figcaption></figcaption></figure>
2. To create an Assertion logic based on the response of a step, go to the "Assertions" tab in the "Step Detail".&#x20;

   <figure><img src="/files/HOhi02wcMXpFUHzRUiWf" alt=""><figcaption></figcaption></figure>
3. You can also join assertions using the 'And' operator. If any assertion does not match the specified value, Ddosify will mark the step as failed.

   <figure><img src="/files/2J3jRSUxgwxDBkUL1SSv" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ddosify.com/ddosify/performance-testing/assertion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.