Runtime settings define the way a Vuser script runs, and can be configured before or after you record a script. These settings are stored in files located in the Vuser script folder. Runtime settings are applied to Vusers when you run a script using VuGen, the Controller, Performance Center, or Business Process Monitor.
Configuring runtime settings allows you to emulate different kinds of user activity. For example, you can emulate a user who responds immediately to output from the server, or a user who stops and thinks before each response. You can also configure the runtime settings to specify how many times the Vuser should repeat its set of actions.
A blue line adjacent to the runtime setting, indicates the current view. The following example indicates that the Think Time runtime setting is active.
You can export runtime settings to a JSON file and import them into another script, instead of having to set them repeatedly for each script. You can also revert the runtime settings back to the default values. For more information, see How to Import and Export Runtime Settings.
Different combinations of runtime settings are available for each protocol. When you open the runtime settings, the relevant runtime setting views for that protocol are listed.
Runtime settings are now a script entity. This allows you to copy or export them for use with other scripts using the shortcut menu.
Tip: Descriptions of the individual runtime settings are available within the runtime settings views, by hovering the mouse over a runtime setting field name.
Runtime Setting Value Validation
The Solution Explorer indicates that one or more runtime settings have illegal values, with a warning icon in place of the standard Runtime Setting node icon, .
If you enter a value above the maximum allowed value, VuGen automatically substitutes it with the maximum allowed value. If you enter a value below the minimum allowed value, VuGen automatically substitutes it with the minimum allowed value.
A red highlighted value, indicates that one of the values in the view is invalid. The following example shows duplicate filter names in the Download Filters view.