How to: Enable or Disable Whether a Scenario Runs During the Warm-Up Period
This topic applies to:
Visual Studio Ultimate |
Visual Studio Premium |
Visual Studio Professional |
Visual Studio Express |
---|---|---|---|
After you create your load test with the New Load Test Wizard, you can use the Load Test Editor to change the scenarios properties to meet your testing needs and goals. For more information, see How to: Create a New Load Test Using the New Load Test Wizard.
Note
For a complete list of the load test scenario properties and their descriptions, see Load Test Scenario Properties.
The Disable During Warmup property is set by using the Properties window. Editing load test scenario properties is set by the Load Test Editor.
The Disable During Warmup property is used to indicate whether the scenario should run or not run during the warm-up period that is specified in the Delay Start Time property. For more information, see How to: Delay the Start Time of a Scenario Using the Load Test Editor.
Note
For a complete list of the run settings properties and their descriptions, see Load Test Scenario Properties.
To enable or disable the warm-up period for a scenario
Open a load test.
The Load Test Editor appears. The load test tree is displayed.
In the load test trees Scenarios folder, click the scenario node that you want to specify the agents to use.
On the View menu, select Properties Window.
The scenario's categories and properties are displayed in the Properties window.
In the Disable During Warmup property, select either True or False.
After you have finished changing the property, click Save on the File menu. You can then run your load test using the new Disable During Warmup value.
See Also
Tasks
How to: Run a Load Test Using Test Controllers and Test Agents Specified in a Test Setting
How to: Delay the Start Time of a Scenario Using the Load Test Editor
Concepts
Other Resources
Editing Load Test Scenarios Using the Load Test Editor
Creating Load Tests Using the New Load Test Wizard
Distributing Load Tests Across Multiple Test Machines Using Test Controllers and Test Agents