Creating a Test

---

After you have planned your Test use Commander to coordinate the Test development process by selecting the Scripts and Collectors you need and combining them into a new Test with the required Task Group settings applied.

Use Task Group settings to control the load generated during a Test-run, which Host is used to run a Task Group and when it starts and stops during a Test-run. Select a Task Group cell in the Test table then use the Properties Window below to apply your settings.

Tests can be developed and then run using remote Hosts across a network to execute the Task Groups that comprise a Test. Distributing Task Groups across a network enables you to run Tests that generate realistic heavy loads simulating the activity of many users. In order to do this, OpenSTA must be installed on each Host and the OpenSTA Name Server must be running on each and configured to specify the Repository Host for the Test.

Tasks and Task Groups

Work from the Repository Window, located by default on the left of the Commander Main Window, to create new Tests and to open existing ones.

The Repository Window displays the contents of the Repository and functions as a picking list from where you can select the Scripts and Collectors you want to include in a Test. Use it in conjunction with the Configuration Tab of the Test Pane to develop the contents of a Test. Select a Script or Collector from the Repository Window then drag and drop it on to a Task column of a Test to create a new Task within a new Task Group.

The Scripts and Collectors you add to a Test are referred to as Tasks. One or a sequence of Script Tasks are represented by a Script-based Task Group. A Collector Task is represented by a Collector-based Task Group. When you add a Script or Collector to a Test, you can apply the Task Group settings you require or you can accept the default settings and return later to edit them.

Some of the Task Group cells in the Test table are dynamically linked to the Properties Window below, select them one at a time to display and edit the associated Task Group settings in the Properties Window.

Select the Start or Host cells in a Task Group row to control the Schedule and Host settings. Script-based Task Groups and the Script Tasks they contain have additional settings associated with them. Select the VUs and Task cells to control the load levels generated when a Test is run.

Use the Disable/Enable Task Group function to control which Task Groups are executed when a Test is run by clicking the check box in the Task Group column cell. This is a useful feature if you want to disable Script-based Task Groups to turn off the HTTP/S load element. The Test can then be used to monitor a target system within a production scenario.

Task Group Settings include:

• Schedule Settings: Control when a Task Group starts and stops to determine the period of data collection during a Test-run.
• Host Settings: Specify the Host computer used to execute a Task Group during a Test-run. The Host computers you use can be local Hosts on your Test network or remote, Web-based Hosts. For more information see Running a Test Over the Web.
• Virtual User Settings: Control the load generated against target WAEs during a Test-run.
• Task Settings: Control the number of times a Script is run and the delay you may want to apply between each iteration of a Script during a Test-run. You can also specify the type of delay, between each Script iteration, which can be either Fixed or Random.

The Test Pane

Use the Test Pane to create and edit a Test, then apply the Task Group settings you require to control how they behave during a Test-run. Run and monitor the Test-run then display your results for analysis.

The Test Pane is displayed in the Main Window when you open a Test by double-clicking a new Test , or an existing Test , in the Repository Window.

The Test Pane comprises three sections represented by the following tabs:

• Configuration: This is the default view when you open a Test and the workspace used to develop a Test. Use it in combination with the Repository Window to select and add Scripts and Collectors. It displays the Test table which has categorized column headings that indicate where Script and Collector Tasks can be placed and the Task Group settings that apply to the contents of the Test.
  Select a Task Group cell to view and edit the associated settings using the Properties Window displayed below the Test table.
• Monitoring: Use this tab to monitor the progress of a Test-run. Select the display options you want from the Monitoring Window, including a Summary and data for individual Task Groups.
• Results: Use this tab to view the results collected during Test-runs in graph and table format. Use the Results Window to select the display options available which are dependent on the type of Test you are running.

Test Pane Features

The Configuration Tab view of the Test Pane is displayed below:

The Test Development Process

The Test development process typically includes the following procedures:

• Create a Test
• Add a Script to a Test
• Add Collectors to a Test
• Define Task Group settings, these include:
• Edit the Task Group Schedule Settings
• Select the Host used to Run a Task Group
• Specify the Number of Virtual Users to run a Script-based Task Group
• Edit the Number of Script Iterations and the Delay Between Iterations
• Save and Close a Test

Create a Test

1. In Commander select File > New Test > Tests.

   Or: In the Repository Window, right-click Tests, and select New Test > Tests.

   The Test appears in the Repository Window with a small crossed red circle over the Test icon , indicating that the file has no content. As soon as you open the Test and add a Script or a Collector, the icon changes to reflect this and appears .

2. In the Repository Window give the Test a name, in this example PRESIDENT_SEARCH, then press Return.

   Note: The new Test is saved automatically in the Repository when you switch to a different function or exit from Commander.

Add a Script to a Test

1. In the Repository Window, locate your new Test and double-click  PRESIDENT_SEARCH, to open it with the Configuration Tab of the Test Pane displayed.

   The Configuration Tab displays the Test table where you can add Tasks, and the Properties Window which is used to apply Task Group settings.

2. Double-click Scripts, in the Repository Window to open the folder.
3. In the Repository Window, click on the FINDBYNAME Script then drag it across to the Test table and drop it in a new row under the Task 1 column.

   The selected Script, FINDBYNAME, appears in the first empty row under the first Task column in a new Task Group. Additional Scripts can be added in sequence within the same row.

• The Task Group name is taken from the Test name and includes a number suffix which is automatically incremented for each new Task Group added to the Test.

  Use the Task Group cell to disable and enable a Task Group.

  Note: Uniquely naming Task Groups enables you to identify and select them for monitoring during a Test-run.

• The Start column indicates the Task Group Schedule settings. For more information on Task Group scheduling, see Edit the Task Group Schedule Settings.
• The Status column displays Task Group activity and status information.
• The Host column defaults to localhost, which refers to the computer you are currently working on.
  The Host you select here determines which computer or device will run the Task Group during a Test-run. For more information on selecting a Host, see Select the Host used to Run a Task Group.
• The VUs column displays the number of Virtual Users assigned to run a Task Group. The default is a single Virtual User 1.
  The number of Virtual Users running the Task Group can be changed by selecting the VUs cell and using the Properties Window to enter a new value. For more information, see Specify the Number of Virtual Users to run a Script-based Task Group.

  With the Script Task you have just added selected, use the Properties Window at the bottom of the Configuration Tab to specify the Task settings. For more information, see Edit the Number of Script Iterations and the Delay Between Iterations.

  Note: If your Task Group incorporates more than one Script, select the next Script from the Repository Window, then drag and drop it into the same Task Group row under the next Task column cell. Repeat this process until your Script sequence is complete.

  You can add additional Scripts to a Test in a new Task Group by dragging and dropping them into the next empty row.

  Note: Your changes are saved automatically in the Repository when you switch to a different function or exit from Commander.

Add Collectors to a Test

1. In the Repository Window, locate your new Test and double-click  PRESIDENT_SEARCH, to open it with the Configuration Tab of the Test Pane displayed.

   The Configuration Tab displays the Test table where you can add Test Tasks and the Properties Window used to apply Task Group settings.

2. Double-click Collectors, in the Repository Window to open the folder and display the contents.
3. In the Repository Window, click on the NT_PERFORMANCE Collector then drag it across to the Test Pane and drop it in a new row under the Task 1 column.

   The selected Collector NT_PERFORMANCE, appears in the next empty row under the first Task column in a new Task Group.

   Note: Collector-based Task Groups can only contain a single Task.

• The Task Group name is taken from the Test name and includes a number suffix which is automatically incremented as new Task Groups are added to the Test.

  Use the Task Group cell to disable and enable a Task Group.

  Note: Uniquely naming Task Groups enables you to select and monitor them during a Test-run from the Monitoring Tab.

• The Start column indicates the Task Group Schedule settings. For more information on Task Group scheduling, see Edit the Number of Script Iterations and the Delay Between Iterations.
• The Status column displays Task Group activity and status information.
• The Host column defaults to localhost, which refers to the computer you are currently working on.

  The Host you select here determines which computer or device will run the Task Group during a Test-run. For more information on selecting a Host, see Select the Host used to Run a Task Group.

4. Repeat step 3, but this time select the SNMP Collector that you created earlier and add it to the Test in the next empty row.

   Note: Your changes are saved automatically in the Repository when you switch to a different function or exit from Commander.

Edit the Task Group Schedule Settings

1. Open a Test with the Configuration Tab of the Test Pane displayed.
2. Click on the Start cell in a Task Group.

   The current Schedule settings are displayed in the Properties Window at the bottom of the Configuration Tab. The default setting is for an Immediate start when the Test is run.

3. In the Start Task Group section of the Properties Window, click to the right of the selection box and choose a Start option:

• Scheduled: The Task Group starts after the number of days and at the time you set.
  Enter a time period using the Days and Time text boxes.
• Immediately: The Task Group starts when the Test is started.
• Delayed: The Task Group starts after the time period you set, (days: hours: minutes: seconds), relative to when the Test was started.
  Enter a time period using the Days and Time text boxes.

  Note: Your settings are displayed in the Test table.

4. In the Stop Task Group section of the Properties Window, click to the right of the selection box and choose a Stop option:

• Manually: The Task Group will run continuously until you click the Stop button in the Status column of the Task Group that activates during a Test run.
• After fixed time: The Task Group is stopped after a fixed period of time.
  Enter a time period using the Time Limit text box.
• On Completion: The Script-based Task Group is stopped after completing a number of iterations.
  Enter the number of Task Group iterations in the Iterations text box.

  Note: Your changes are saved automatically in the Repository when you switch to a different function in or exit from Commander.

  Note: During a Test-run Schedule settings cannot be edited, but they can be overridden manually using the Start and Stop buttons in the Status column of each Task Group.

Select the Host used to Run a Task Group

Note: Collector-based Task Groups include a Collector which defines a set of data to be recorded from one or more target Hosts during a Test-run. The Host you select in the Test table determines which computer or device will run the Task Group during a Test-run, not the Host from which data is collected.

1. Make sure the PRESIDENT_SEARCH Test is open with the Configuration Tab of the Test Pane displayed.
2. Click on the Host cell in a Task Group.

   The current Host settings are displayed in the Properties Window at the bottom of the Configuration Tab. The default setting is localhost, which refers to the computer you are currently using.

3. In the Host Name text box of the Properties Window, enter the name of the Host to run the Task Group. Your settings are then displayed in the Test table.

   Note: The Host you select must have the OpenSTA Name Server installed and running with the Repository Host setting pointing to the local Host.

   Note: Your changes are saved automatically in the Repository when you switch to a different function in or exit from Commander.

Specify the Number of Virtual Users to run a Script-based Task Group

You can accept the default settings for your first Test-run then experiment with the settings to increase the load and compare Test-run results.

1. Make sure the PRESIDENT_SEARCH Test is open with the Configuration Tab of the Test Pane displayed.
2. Click on the VUs cell of the Task Group whose Virtual User settings you want to edit. The current Virtual User settings are displayed in the Properties Window at the bottom of the Configuration Tab. Use it to help control the load generated during a Test-run by specifying the number of Virtual Users and when they start.
3. In the Properties Window enter a value in the first text box to specify the total number of Virtual Users for the Task Group, or use to set a value.
4. Select the Logging level required for the Task Group to control the level of performance statistics and Timers gathered from Virtual Users. Click , and select either:
   Low: Information collected from the first 10 Virtual Users in the Task Group.
   High: Information collected from all the Virtual Users in the Task Group.
   None: No performance statistics or Timers are gathered.
5. Click the Generate Timers For Each Page check box, to record results data for the time taken to load each Web page specified in the Scripts, for every Virtual User running the Scripts. Timer information is recorded for the duration of the complete Script if the box is checked or unchecked.
6. Click on the Introduce Virtual Users in batches check box if you want to ramp up the load you generate by controlling when the Virtual Users you have assigned run. This is achieved by starting groups of Virtual Users in user defined batches.
7. Use the Batch Start Options section to control your Virtual user batch settings.

• Interval between batches, specifies the period of time in seconds between each ramp up period. No new Virtual Users start during this time.
• Number of Virtual Users per batch, specifies how many Virtual Users start during the batch ramp up time.
• Batch ramp up time (seconds), specifies the period during which the Virtual Users you have assigned to a batch start the Task Group. The start point for each Virtual User is evenly staggered across this period.

  The example below depicts the Properties Window, where 20 Virtual Users are assigned to a Script-based Task Group.

  When the Task Group is run 2 Virtual Users (the number of Virtual Users per batch) will start over a period of 5 seconds (batch ramp up time) with a 10 second delay between each batch running.

  

  Note: Your changes are saved automatically in the Repository when you switch to a different function in or exit from Commander.

Edit the Number of Script Iterations and the Delay Between Iterations

You can accept the default settings for your first Test-run then experiment with the settings to increase the load and compare Test-run results.

1. Make sure the PRESIDENT_SEARCH Test is open with the Configuration Tab of the Test Pane displayed.
2. Click on the FINDBYNAME Script Task in the Test table, to display the current Task settings in the Properties Window at the bottom of the Configuration Tab.
3. With a Script Task selected, use the Properties Window to specify how long the Task runs. Click on the Task Termination box and select an option, either:

• On Completion: set a value to control the number of times (iterations) a Virtual User will run the Script during a Test-run.
• After Fixed Time, specify a time period to control when the task completes.

  Enter a value in the text box below or use .

4. You can specify a Fixed or Variable delay between each iteration of a Script Task.
   In the Properties Window, click on the Delay Between Each Iteration box and select an option, either:

• Fixed Delay: set a time value in seconds using the Delay text box.

  Or, you can choose to introduce a variable delay between Scripts:

• Variable Delay: set a value range in seconds using the Minimum and Maximum text boxes to control the upper and lower limits of variable iteration delay.

  Note: Your changes are saved automatically in the Repository when you switch to a different function in or exit from Commander.

Save and Close a Test

• The Test related work you perform is automatically saved in the Repository and the Test is closed when you switch to a different function or exit Commander.

Next...

After you have created a Test, by adding a Scripts and Collector, and applied the Task Group settings required, you are ready to run it against the demonstration Web site.
Move on to the next section for details on how to do this.

Next Section: Running a Test

Back to Contents