![]() |
![]() |
![]() |
![]() |
Test Development
Commander provides a flexible Test structure which enables you to quickly develop Tests that accurately simulate the web activity you want to examine.
In its simplest form a Test can consist of just one Task Group running a single Script with no data collection Profiles, relying on the default data collection categories to collect results data during a Test run. However, to produce a fully automated performance Test that accurately simulates the test scenario you want, as well as generating the quality of results data required, it is usually necessary to develop a more detailed Test structure. Use Commander to create Tests incorporating Script-based Task Groups, which can include a number of sequenced Scripts, and if required, Profile-based Task Groups to collect additional performance results data. Commander enables you to create a reliable and repeatable test process, which can be guaranteed to start up and execute correctly each time.
After you have produced a performance Test plan you need to develop it by creating the contents of your Tests. Use Commander to launch Script Modeler to create Scripts, and the NT Performance and SNMP packages to create Profiles. Coordinate Test development using Commander to select Scripts and Profiles and combine them into a new Test.
Control the load generated during a Test run by adjusting the default Task Group attributes. Then specify which Host computers you want to use during a Test run. Run the Test to simulate real end user activity and accurately reproduce the Test conditions you want.
Display Test results to assist in the analysis of the target web site's design. Use Commander to modify the Test contents and parameters in order to control the load generated during a Test run and to produce the results you need.
Test Creation
Use Commander to launch the HTTP/S Load software packages needed to create the Scripts and Profiles you require for your Test. Use the right-click menu function associated with the
Scripts folder to Launch Script Modeler and create a new Script, or select File > New Script > HTTP in the Menu Bar. If you want to include data collection Profiles, right-click the
Profiles folder or select File > New Profile > SNMP or NT Performance in the Menu Bar to launch NT Performance and SNMP packages.
Now you are ready to create a new Test and incorporate the Scripts and Profiles you need. Use the right-click menu function associated with the
Tests folder to create a new Test, or select File > New Test > Tests in the Menu Bar. Give your Test a name, then double-click the Test in the Repository Window to open it in the Configuration tab view of the Active Test Pane. You are presented with a table display where you can develop the contents of the Test by selecting the Scripts and Profiles you need from the Repository Window. Drag and drop them under the Task columns of the Test table in the order you want. Scripts and Profiles are included in Tests by reference, which means they can be included in many Tests without duplication or changing the settings of the original Scripts and Profiles.
The Scripts and Profiles you add to a Test are known as Tasks which are represented by Task Groups in separate rows within the Test table. Scripts and Profile Task Groups are mutually exclusive. Script-based Task Groups can support a single Script or a modular sequences of Scripts, whereas Profile-based Task Groups include a single Profile. There is no limit to the number of Task Groups you can add to a Test.
You can set the Task Group attribute for each Task Group included in a Test. For example, increasing the number of Virtual Users, raises the load level generated against a target web site during a Test run. You can also specify which Hosts computers are used to perform each Task Group during a Test run.
Tests must be defined according to the rules for OpenSTA Datanames and are stored in the Repository. When you create a new Test, a folder bearing the name of the Test is created, for example:
After you have added the Scripts and Profiles you need and applied the Task Group attributes required, the Test is ready to run. Compile, then run the Test.
The Active Test Pane
The Configuration tab view of the Active 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. It presented a table display where you can create and edit Tests.
Use the Repository Window in combination with the Active Test Pane to select the Scripts and Profiles you want to include and to build a new Test. Work within the Active Test Pane to apply the Task Group attributes you want to the Task Groups that represent the contents of your Test.
The Active Test Pane comprises three sections represented by the following tabs:
·Configuration: This is the default display when you open a Test. It displays a table with categorized column headings that indicate where Scripts and Profiles can be placed. Use the functions provided here to build a Test. Select the Scripts and Profiles you need from the Repository Window, then drag and drop them under the Task columns of the Test table in the order you want. Specify the Task Group attributes for the Task Groups you include.
·Monitoring: Click on this tab to monitor the progress of a Test during execution. Display a progress summary or monitor a specific Test Task Group.
·Results: Click on this tab to view the results data collected during a Test run in graph and table format, connected to specific Task Groups.
Creating Tests working in the Repository Window and Active Test Pane
Work from the Repository Window, located by default on the left of the Commander Main Window, to create and open Tests. It displays the contents of the Repository and functions as a picking list from where you can select the Scripts and Profiles you want to add to a Test.
Drag and drop your selections one at a time on to the Task columns of the Active Test Pane. Each row you add to your Test structure represents a separate task within the Test known as a Task Group. A Task Group can contain one or more Scripts or a single data collection Profile but not both.
When you add a Script to a Test a new Task Group is automatically created and the Script Definition dialog appears, which enables you to specify some of your Task Group attributes. You can either accept the default values or specify a new value to control the number of times each Virtual User runs a Script and the delay you want to apply between each iteration of a Script.
Control the load generated against target web sites during a Test run by specifying the number of Virtual Users assigned to each Script-based Task Group. Double-click on the VUs column table cell within a Task Group to specify how many Virtual Users you need. Specify which Host computers you want to run the Task Groups by double-clicking on the Host column table cell within a Task Group and defining a networked Host computer.
Scripts and Profiles that you incorporate in a Test can be removed by overwriting them with new selections or by deleting them from the Active Test Pane.
The Test Development Process
The Test development process typically includes the following procedures:
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 Profile, the icon changes to reflect this and appears
.
2 Give the new Test a name within the Repository Window, which must be an OpenSTA Dataname, and press Return.
Note: This procedure can be carried out no matter what other tasks you have been performing in the Main Window.
2 Double-click a new Test, or an existing Test
, to open the Active Test Pane in the Commander Main Window.
The Configuration tab of the Active Test Pane presents you with an empty table where you can add the contents of your Test and apply Task Group attributes.
Note: This procedure can be carried out no matter what other tasks you have been performing in the Main Window.
3 Click on a Script then drag it across to the Active Test Pane and drop it in a new row under the Task 1 column, as shown below:![]()
· The selected Script,Script 1, appears in the first row under the first Task column as a new Task Group.
· The Task Group name is taken from the Test name and is automatically incremented as additional Task Groups are added to the Test.
Note: Uniquely labelling each Task Group enables you to select to monitor a Task Group during a Test run by clicking on the Monitoring tab of the Active Test Pane and selecting a Task Group from the list.
· The Host column defaults tolocalhost, which refers to the computer you are currently working on and indicates which computer will run the Task or Tasks defined by a Task Group. The Host can be changed by double-clicking on this table cell and entering the name of a new Host or selecting one from the list.
· The VUs column displays the number of Virtual Users assigned to a Task Group. The default is a single Virtual User1. Double-click on this table cell and specifying your Task Group attributes.
4 The Script Definitions dialog box appears automatically after you drag and drop a Script into the Active Test Pane. You are prompted to specify the number of times, or the number of iterations, a Virtual User will run the Script during the Test run. Enter a value in the Iterations text box.
5 If required you can specify a Fixed or Variable delay between each Script iteration. Or you can click OK to accept the default settings and return later to edit your Task Group attributes if you choose.
· Click Variable Delay and enter a time value in seconds in the Min and Max text boxes to set the upper and lower limits of variable iteration delay.
Note: Double click a Script to re-open the Script Definitions dialog box to edit your Task Group attributes.
7 If your Task Group incorporates more than one Script, select the next Script from the Repository Window and drag and drop it into the same row as the first Script under the next Task column. Repeat this process until your Script sequence is complete.
8 Add additional Scripts as part of a new Task Group by dragging and dropping a Script onto the next row down.
3 Click on a Profile then drag it across to the Active Test Pane and drop it in a new row under the Task 1 column, as shown below:![]()
· The Profiles selected in the example aboveProfile 1-NT and
Profile 2-SNMP, appear in the second and third rows under the first Task column in separate Task Groups. A Profile based Task Group can only contain a single Task.
· The Task Group name is taken from the Test name and is automatically incremented as additional Task Groups are added to the Test.
Note: Uniquely labelling each Task Group enables you to select to monitor a Task Group during a Test run by clicking on the Monitoring tab of the Active Test Pane and selecting a Task Group from the list.
· The Host column defaults tolocalhost, which refers to the computer you are currently working on and indicates which computer will run the Task Group. The Host can be changed by double-clicking on this table cell and entering the name of a new Host or selecting one from the list.
Note: Your changes are saved automatically when you switch to a different task in or when you exit Commander.
3 In the Script Definitions dialog box specify the number of times, or the number of iterations, a Virtual User will run the Task during a Test run. Enter a value in the Iterations text box.
· Click Variable Delay and enter a time value in seconds in the Min and Max text boxes to set the upper and lower limits of variable iteration delay.
Note: Profiles are included in a Test by reference which means they can be used in other Tests without duplicating or changing the original Profile.
2 Double-click on the VUs column, of the Task Group you want to edit.
In the Task Group Definitions dialog box select enter the number of Virtual Users who will perform this Task in the text box.
5 Select the Logging level required for this Task Group, which determines the level of performance statistics gathered from Host computers. Click and select either:
6 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.
3 In the Host Definition dialog box enter a computer name in the text box or select one from the list.
The Script or Profile that you remove is not deleted from the Repository since they are included in Tests by reference.
Note: Scripts and Profiles are included in a Test by reference which means they can be used in other Tests without duplicating or changing the original Profile.
2 Select the Script or Profile you want from the Repository Window and drag and drop it onto the Task (a Script or Profile) in the Active Test Pane that you want to replace.
The Script or Profile that you overwrite is not deleted from the Repository since they are included in Tests by reference.
Note: Your changes are saved automatically when you switch to a different task in or when you exit Commander.
When you have finished creating a Test you need to compile it to check the integrity of the Scripts contained and to generate a .TOF file which is used to execute the Test. It is good practice to compile your Scripts as you create them in Script Modeler.
3 When your Test compiles successfully you are notified with an on-screen message. Click OK in the dialog.
A Compile Errors dialog appears if compilation is unsuccessful, detailing the nature of the problem.
Note: If you have not compiled a Test before you run it, clicking the Test Run button, automatically compiles the Test.
· The Test related work you perform is saved when you switch to a different function or when you exit Commander.
CYRANO Customer Support: France +33 (0) 1 56 33 40 00 USA +1 (978) 462-0737 UK +44 (0) 1274 761024 support-fr@cyrano.com support-us@cyrano.com support-uk@cyrano.com |
![]() |
![]() |
![]() |
![]() |