Ddosify Scenario Builder
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
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.
Caution: Don't put query parameters in the target field. There is a section for query parameters in the Step Details section.
For example, instead of
q=termparameter to the key-value form in Step Details modal.
- Click the New Step button if you would like to add another step to the scenario.
You can provide query parameters, request headers, payload, authentication, and network details of the request here. You can also Capture Variables and create Assertion logic in Step Detail.