Open System Testing Architecture

TOC PREV NEXT INDEX



Overview of HTTP/S Load
· The HTTP/S Load Package
· Core Functions of HTTP/S Load
· Using HTTP/S Load
· The Commander Interface
· Commander Toolbars and Function Bars
· The Commander Main Window
· The Repository Window

The HTTP/S Load Package

HTTP/S Load combines HTTP and HTTPS recording and modeling functionality with Test creation and data collection. It takes full advantage of the low system resources required for dedicated HTTP/S recording and replay, enabling you to carry out large volume performance Tests with minimum replay resources.

Commander runs within the OpenSTA Architecture and is used to create and run Tests, then display results for analysis. In Commander a Test consists of Task Groups, which structure and control the contents of a Test. A Test must include at least one Task Group incoporating one or more Scripts. A Test can also include Profile-based Task Groups containing a data collection Profile.

Scripts form the basis of your Tests. They are created from the recordings of the HTTP/S traffic generated during a web session and written in SCL scripting language, which enables you to model their content. They encapsulate the web activity you need to test and enable you to reproduce the required test conditions when they are run as part of a Test. A profile is a collection of queries which determine the data collection carried out when a Test is run.

Use Commander to create Tests by selecting the Scripts and Profiles you need from the Repository where they are stored and adding them by reference to Tests as new Task Groups. Specify the Task Group attributes for each Task Group you include to control the load generated during a Test run and to specify which Host computers are used to run each Task Group.

Run Tests to simulate the activity of real end users and produce the results you need to measure the efficiency of target web sites.

Creating Scripts and Profiles is a separate process from the creation of the Tests and can be conducted independently.

Core Functions of HTTP/S Load

HTTP/S Load combines HTTP/S recording and modeling functionality with Test creation and system data collection, to help you performance Test web sites. It's easy to use features enable you to quickly develop and run Tests to simulate the web activity you need to test.

All Test develepment procedures are initiated from Commander. Use it to create Tests and to coordinate the develepment process.

Performance test a web site using HTTP/S Load:
1 Create Scripts (Script Modeler).
2 Model Scripts if required (Script Modeler).
3 Create data collection Profiles - optional
(SNMP, NT Performance Monitor).
4 Create Tests, by adding Task Groups containing the Scripts and Profiles required (Commander).
5 Define Task Group attributes (Commander), including:
· Host computers used to run a Task Group - Script and Profile Task Groups
· Number of Virtual Users assigned - Script-based Task Groups only
· Script definition; including the number of Script iterations and the delay between iterations during a Test run - Script-based Task Groups only
6 Run a Test (Commander).
7 Monitor a Test run (Commander).
8 Display the Test results (Commander).

Note: It is not necessary to stick rigidly to this procedural sequence. HTTP/S Load is flexible and enables you to work in ways that best suit you and the procedures you need to perform.

Related Topics:
· Using HTTP/S Load
· Working With Tests

Using HTTP/S Load

HTTP/S Load can be used in a variety of ways according to the needs of different users. It supplies modular software in which the creation of Scripts, Profiles and Tests are separate processes that can be conducted independently. For Example, if you are involved in Script or Profile creation, you can launch Commander and create new Scripts and Profiles without creating a new Test first.

Use Commander to initiate all Test development procedures. The main areas of procedure supported by HTTP/S Load are summarized below:

Creating Tests

The Tests you create using HTTP/S Load to evaluate web site performance, can include all the elements necessary to accurately simulate the type of activity and the numbers of users you need. The Test creation process incorporates the full range of performance testing procedure and provides you with a framework on which you can develop transparent, easy to maintain Tests.

Test creation involves first creating, then selecting the Scripts and Profiles you want to include and then applying the performance Test conditions you need, in order to simulate the required conditions. Executing or running Tests enables you to imitate real end user activity and accurately simulate the environment you want. After you have created the Scripts and Profiles you need, create a new Test and select the ones you want to include. For more information see Creating and Editing Tests.

Recording Scripts

Script recording involves deciding how you expect clients to use the web site under test and then recording the web activity. Scripts represent the content of your performance Test, so careful planning of your recordings is essential.

Browser output and web site responses are automatically recorded at the HTTP/S level using the OpenSTA Gateway, This component is launched when you begin recording a Script using Script Modeler. The Gateway produces Scripts which are represents using SCL scripting language. This SCL encoding gives you the option of modeling Scripts by editing and enhancing the code to represent multiple virtual users when a Test is run.

Script recording is a process that can be carried out independently of Test generation. For more information Recording Scripts.

Modeling Scripts

Script modeling involves editing a recorded Script so that it can be applied in a web site performance Test to function as one or more virtual users.

Modeling Scripts is not an essential procedure, particularly if the web site under test comprises static content only. But it is a useful facility if you need to capture the dynamic changes of a web site during a session. For example, you may need to enter a unique user name and password for each virtual user, so that the Test accurately simulates real end user activity when it is executed. You can achieve this by capturing a Script then modeling it to include a variable that changes the user name and password for each user, every time the original Script is run as part of a Test. So with one modeled Script you can create all the virtual users you need, each using his or her own unique account just like real end users.

Use the Script Modeler to record the web activity you need to test and to edit Scripts. For more information see Recording Scripts and Modeling Scripts.

Profile Creation

A Profile is a collection of user defined queries which determine the data collection carried out during a Test run. Profile creation involves launching an OpenSTA system monitoring package such as SNMP or NT Performance Monitor and specifying the type of web application environment data to be collected, and which host computers to monitor. Profiles to monitor the system's performance during a Test run.

Profile creation is a process that can be carried out independently of Test generation. For more information see Creating and Editing Profiles.

Running and Monitoring Tests

Use Commander to create performance tests then execute and monitor the Test run. Running a test enables you to imitate real end user web activity and accurately simulate the test conditions you want by generating the level of load required against target web sites.

You can monitor the progress of a Test run by selecting the Task Groups included and tracking the Scripts and the Virtual Users that are currently running the Test. You can also add Profile-based Task Groups to a Test which can be monitored by selecting the data collection queries defined in the Profile and displaying them in graphs. For more information see Executing and Monitoring Tests.

Results Display

HTTP/S Load graphs both virtual user response times and resource utilization information from all web sites under test.

Executing a test and analyzing the results enables you to identify whether a web site is able to meet the processing demands you anticipate will be placed on it. HTTP/S Load provides a variety of data collection and display options to assist you in the analysis of test results. When a test is run a wide range of data is generated automatically. Virtual user response times and resource utilization information is recorded from all web sites under test, along with performance data from the host computers used to run the test.

After a test run is complete the results can be displayed to assist you in the analysis of a web sites' performance and the network over which the test was run. Open the test you want from the Repository Window and click on the Results tab in the Active Test Pane, then select the results you want to display.

The Commander Interface

Commander supports a flexible and intuitive user interface which gives you a high degree of visibility and control over the elements you need to manipulate in order to successfully develop performance tests.

Use the menu options or work from the Repository Window to initiate the creation of Profiles, scripts and tests. Right-click on the Repository Window folders and choose from the functions available. The options you choose and the test elements you select here instantly invoke the module that supports them within the Commander Main Window (with the exception of Script Modeler which is launched in a new window). Once a module is launched, make use of the functionality provided through the Main Window by clicking on the tabs and other constituents and select from the options available.

After you have created or edited a test or Profile in the Main Window they are automatically saved.

The Commander interface is divided up into three primary areas:

· Commander Toolbars and Function Bars.
· The Repository Window.
· The Commander Main Window.
Commander Interface Features

The main features of the Commander interface are detailed below:

Commander Toolbars and Function Bars

Toolbars

When you first open up Commander no toolbars are visible. The toolbars that appear in the Main Window will vary depending on the module you have invoked to implement a task. Refer to specific modules for details.

Can float toolbars over the Main Window to increase the workspace area.

Function Bars
· Title Bar: Displays the Commander Control Icon , which gives you access to the Control menu. It also incorporates the standard Windows buttons Minimize, Restore/Maximize and Close.
· Menu Bar: Displays Commander menu options. The menu options available in the Menu Bar will vary depending on the module you have invoked to implement a task. Refer to specific modules for details.
Click on a menu option or use the keyboard shortcuts to access and select the functions you need.
Note: Some of these menu functions can also be accessed by right-clicking on the default folders within the Repository Window and using the menu options provided.
· Status Bar: Displays information relating to the current document.
Click View > Status Bar to hide and display it.
Toolbar Display Options

Commander toolbars are located below the Menu Bar.

You can choose to display or hide toolbars using the View menu option to maximize the workspace available in the Main Window.

Hide/Display Toolbars
· Click View > Toolbar.
A tick to the left of the toolbar listed indicates that it is currently displayed.

The Commander Main Window

The Commander Main Window is located below the Menu Bar and functions as a workspace and container for the creation of data collection Profiles and test development. SNMP and NT Performance Monitor modules are displayed here when you launch them to create Profiles.

The Active Test Pane is displayed in the Main Window when you create or edit a test by double-clicking or , in the Repository Window.

The Repository Window is also located in the Main Window. Use it to launch the modules required to create the scripts, Profiles and tests you need.

Main Window Display Options

Resize the Main Window to increase your workspace area by manipulating the Repository Window.

You can adjust the borders of the Repository Window or float it over the Main Window. You can also close the Repository Window to maximize the workspace display area by clicking , in the top right-hand corner of the window. To display the Repository Window select Tools > Show Repository.

Resize the Main Window
· Click on the border of a window and drag it to the required position.

Hide/Display the Status Bar

The Status Bar can be hidden to give you a larger workspace.

· Click View > Status Bar to toggle display.

The Repository Window

After you have planned your performance test you can work from the Repository Window to initiate and conduct many test related tasks. You can kick off the creation of Profiles and scripts from here as well as generating and maintaining tests. Use the Repository Window to manage the contents of the Repository by adding, editing and removing Profiles, scripts and tests.

The Repository Window is located on the left-hand side of the Main Window and displays the contents of the Repository in three default folders; Profiles, Scripts, and Tests. These folders organize the contents of the Repository according to the attributes of the components stored here, as well as providing the functionality associated with the test elements and tests. They represent the modules and functionality you have installed on your computer and will vary according to the configuration you have chosen.

Use the Repository Window to launch the modules and functions required to create, display and edit Profiles, scripts and tests. Work from within it to access all test related data that is stored in the Repository including scripts, Profiles, tests and results.

Within the Repository Window directory structure, double-click on  Profiles, Scripts, and Tests to open them and display the information they contain. Right-click on the folders and files displayed to view the menu options associated with them, then choose from the options available.

When you double click on a Profile or test in the Repository Window, the module or plug-in associated with it is launched in the Main Window. Scripts are supported by the Script Modeler which is launched in a separate window when you double-click on a script or choose to create a new one.

You can also add new folders and use them to group related tests to help you manage the contents of the Repository and organize your tests.

The test data stored in the Repository is organized alphabetically and can be deleted by using the right-click menu option associated with every test component. The order and appearance of the default folders, Profiles, Scripts and Tests, cannot be modified from within Commander. They can only be removed by uninstalling the software module associated with them.

You can also select a new Repository Path if you need to share tests and tests elements across a network.

Profiles Folder

The Profiles folder displays all the Profiles stored in the Repository and supports a variety of Profile related functions. Right-click on this folder to access the menu options available.

The NT Performance Monitor and, or, the SNMP modules must be installed before the Profiles folder appears in the Repository Window.

Open the Profiles folder and display the Profiles contained by double-clicking Profiles  .

Profiles Folder and Profiles, Display Options and Functions
· Double-click Profiles, to expand or collapse the directory structure.
· Right-click Profiles, to display a pop-up menu from where you can choose to create a New Profile.
· Double-click on a new Profile (NT Performance) or (SNMP), to launch the software module associated with it and specify your data collection queries.
When you first create a Profile no data collection queries have been defined, so it appears with a small crossed red circle over the Profile icon to indicate this status, or . After you have defined your Profile settings, the cross is removed, (NT Performance) or (SNMP).
· Double-click on a Profile or , to launch the software module associated with it and make any edits required to the files.
· Right-click on a Profile or , to display a pop-up menu which gives you the option to Edit, Rename or Delete the Profile from the Repository.
Note: Profiles are included in tests by reference, so editing the data collection queries of a Profile after they have been incorporated into a test, affects all the tests that use them. Renaming or deleting Profiles removes them from all tests that use them.

Scripts Folder

The Scripts folder displays all the scripts stored in the Repository and supports a variety of Script related functions. Right-click on this folder to access the menu options available.

The Script Modeler software module must be installed before the Scripts folder appears in the Repository Window.

Open the Scripts folder and display your scripts by double-clicking Scripts  .

Scripts Folder and Scripts, Display Options and Functions
· Double-click Scripts, to expand or collapse the directory structure.
· Right-click Scripts, to display a pop-up menu from where you can create a New Script.
· Double-click on a new script , to launch Script Modeler and record the web activity you want and model the script.
When you first create a script it contains no data because no HTTP/S recording has been performed, so it appears with a small crossed red circle over the Profile icon to indicate this status . After you have recorded the script, the cross is removed, .
· Double-click on a script , to launch Script Modeler and model the script.
· Right-click on a script , to display a pop-up menu which gives you the option to Edit, Rename or Delete the script from the Repository.
Note: Scripts are included in tests by reference, so modeling them after they have been incorporated into a test affects all the tests that use them. Renaming or deleting scripts removes them from all tests that use them.

Tests Folder

The Tests folder displays all the Tests stored in the Repository and supports a variety of test related functions. Right-click on this folder to access the menu options available.

Open the Tests folder and display your tests by double-clicking Tests  .

When you first run Commander the Tests folder is empty. It is the only default folder that appears if you have opted for the minimal installation option excluding additional modules.

Tests Folder and Tests, Display Options and Functions
· Double-click Tests, to expand or collapse the directory structure.
· Right-click Tests, to display a pop-up menu from where you can create a New Folder or a New Test.
· Double-click on a new test , to display the Active Test Pane in the Main Window, where you can add scripts and Profiles to construct your test contents and apply your test parameters..
When you first create a test it contains no scripts or Profiles, so it appears with a small crossed red circle over the test icon to indicate this status . After you have recorded the script, the cross is removed, .
· Double-click on a test , to display the Active Test Pane in the Main Window, where you can add, remove and reorganize scripts and Profiles, and edit your test parameters.
· Right-click on a test , to display a pop-up menu which gives you the option to Edit, Rename or Delete the test from the Repository.
Note: All the test elements incorporated into a test are included by reference, so editing, renaming or deleting tests does not affect the scripts and Profiles they contain.

Repository Window Display Options

The Repository window is located on the left-hand side of the Main window by default. You can hide it to increase the Main Window workspace area available, move it to a new position or float it over the Main Window.

Hide/Display The Repository Window
· Click , in the double bar at the top right-hand side of the Repository Window to close it.
· Select Tools > Show Repository to display the Repository Window.
Move The Repository Window
1 Click on the double bar at the top of the Repository Window.
2 Drag, then drop it in the new position within the Main Window.
Note: The Repository Window docks with the Main Window's borders if it contacts them.
Resize The Repository Window
1 Move your cursor over part of the window edge.
2 Click and drag, then drop the border in the required position.
Select a New Repository Path
1 In Commander select Tools > Repository Path.
2 In the Browse for folder dialog box, select a new Repository path by moving through the directory structure displayed and choose the location you want.
3 Click OK to create a new Repository.
Note: You can create several Repositories and use them to store different performance test projects. This procedure creates a new Repository if none exists in the location you choose, or switches the Repository Path to reference an existing Repository.


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
TOC PREV NEXT INDEX