### What is Scenario?
In essence, a scenario represents a series of steps designed to mimic the actions of an end-user. This end-user could be a real person using a browser to access your website or another software program that sends API requests to your endpoints.
For instance, imagine you own an e-commerce business and wish to evaluate the performance of the following user flow:
1. User visits the home page
2. User logs in
3. User adds a product to the shopping cart
To accomplish this, you must construct a scenario containing these 3 steps. It is essential to ensure that the steps are executed in the correct order, as the sequence is critical to accurately simulating the end-user's experience.
Ddosify Load Testing Example Scenario
### What is a Step?
Step represents the individual network request.
* **Step Name** is not mandatory. But it is nice to have since you can easily distinguish your steps on the Test Report page if you provide it.
* **Target** is where you supply network protocol and URL.
* **Method** is the HTTP method.
{% hint style="warning" %}
**Caution:** Don't put query parameters in the target field. There is a section for query parameters in the [Step Details](#step-details) section.
For example, instead of **`http://example.com/search?q=term`** write **`http://example.com/search`** and put **`q=term`** parameter to the key-value form in [Step Details](#step-details) modal.
{% endhint %}
* Click the **New Step** button if you would like to add another step to the scenario.
* Click the 'More' (three-dot icon at the right) button to provide [Step Details](#step-details).
#### Step Details
You can provide query parameters, request headers, payload, authentication, and network details of the request here. You can also [Capture Variables](https://docs.ddosify.com/ddosify/performance-testing/correlation) and create [Assertion](https://docs.ddosify.com/ddosify/performance-testing/assertion) logic in Step Detail.
#### Other Important Concepts on Scenario Builder
* [Parametrization](https://docs.ddosify.com/ddosify/performance-testing/parametrization)
* [Test Data](https://docs.ddosify.com/ddosify/performance-testing/test-data-import)
* [Environments](https://docs.ddosify.com/ddosify/performance-testing/environment-variables)
* [Correlation](https://docs.ddosify.com/ddosify/performance-testing/correlation)
* [Assertion](https://docs.ddosify.com/ddosify/performance-testing/assertion)
* [Debugging](https://docs.ddosify.com/ddosify/performance-testing/debugging)
* [Postman Import](https://docs.ddosify.com/ddosify/performance-testing/postman-import)
---
# 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/test-suite/scenario-flow.md?ask=
```
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.
