Requests in recorded scenarios can include parameters sent by a user to the tested web application. For example, user credentials, web form data, search queries, and so on.
When you simulate the recorded scenario of multiple virtual users, they will send identical requests that may be unrealistic.
To simulate real-life conditions, you can parameterize your recorded scenario, that is, replace recorded request parameters with variable values. This way you can provide each virtual user in a scenario with individual test data.
This topic describes how you can parameterize scenarios manually in the Scenario editor.
Analyze the scenario you want to parameterize. Find requests containing parameters you want to replace with variables, learn what data these parameters store.
|Note:||In LoadComplete, user scenarios can store up to 50 MB of data for a response. If the values you need are beyond this bound, they will not be parameterized.|
In the Variables editor, create variables that will supply your scenario with needed test data. Specify how these variables will change their value on each use.
|Note:||We recommend that you create a variable whose data matches the parameter’s data type. If LoadComplete fails to convert the variable value to the parameterLoadComplete data type, the tested web server may raise an error.|
After you create the variable that will supply the scenario with needed test data, replace the parameters in the request with the variable: