open sta info -final.pptx

7/31/2019 Open STA Info -final.pptx

1/28

Open STA

Performance Testing Tool

Alok Sinha

Shubankar RaySNAPDEAL.COM


2/28

Open STA- Topics covered

Commander

Creating scripts

Script modeler Recording and Modeling scripts

Creating and editing Tests

Result Analysis


3/28

Open STA Overview

OpenSTA is a Load and performance

monitoring tool for web application

environment. It works on http/s requests.

OpenSTA has two sub components you should

be aware of

OpenSTA Commander

OpenSTA Script Modeler


4/28

Overview Continued

HTTP/S Load is an ideal tool for performance testing WebApplication Environments (WAEs). It supplies versatile software thatenables you to create and run HTTP/S load Tests and productionmonitoring Tests to help evaluate target systems.

HTTP/S Load enables you to run Tests against the same targetsystem within both load testing and production monitoringscenarios. Tests can include an HTTP/S load element to help youevaluate the performance of WAEs during development. Tests canalso be used to monitor and collect performance data from WAEsafter they go live within a production scenario. Results data iscollected during Test-runs and can be displayed for analysis duringor after a Test-run, enabling you to directly compare theperformance of a target system within these two environments.


5/28

Open STA Commander


6/28

Open STA Commander

Commander is the Graphical User Interface

that runs within the OpenSTA Architecture

and functions as the front end for all Test

development activity. It is the program you

need to run in order to use OpenSTA.

Launch Commander

Click Start > Programs > OpenSTA > OpenSTA

Commander.


7/28

Open STA Commander

The Commander interface is divided up into

three primary areas:

Commander Toolbars and Function Bars.

The Repository Window.

The Commander Main Window.


8/28

Recording a script

Scripts form the content of an HTTP/Sperformance Test using OpenSTA.

Script creation involves:

Create a New Script Using Commander

Familiarizing yourself with the Script Modeler

Planning your Script Configuring Script Modeler for Script Creation

Recording a Web Session


9/28

Create a New Script Using

Commander

1. In Commander select File > New Script >

HTTP. Or: In the Repository Window, right-

click Scripts, and select New Script > HTTP.

2. After you have created an empty Script it

appears in the Repository Window, Scripts

folder.

Double-click the new Scriptto launch Script

Modeler.


10/28

Script Modeler Interface


11/28

After you create a Script or when you open one, it isdisplayed in the Script Pane on the left-hand side of themain window. It is represented using SCL code whichenables you to model it using the menu options or directlyby keying in the SCL commands you need.

The Query Results Pane is used to display Web siteresponses. HTML information is recorded during the sameWeb session as the corresponding Script and is directlyrelated to it, which enables additional modeling options.

The Output Pane. Displays the results of Script compilation.Scripts need to be compiled after modeling to check thevalidity.


12/28

Configuration for Script Modeler

Selecting the type of browser you want to use to record Scripts. In Script Modeler, select Options > Browser

In the Select Browser dialog box, click , and select the browser youwant to use from the list, either Internet Explorer 4, Internet Explorer5 or Netscape.

Click OK to save your settings

Ensuring that your browsers proxy server settings are correctlyconfigured.

Script Modeler's recording mechanism makes use of a proxy server,

known as the Gateway, which is used to intercept and record theHTTP/S traffic generated during a Web session.


13/28

Recording a Web Session

After you have selected a browser and configured the Gateway, youare ready to record a Web session and create a Script.

Open the script Modeler

Click the Record button , in the Capture/Replay Toolbar, or selectCapture > Record, to begin the HTTP/S capture process.

This action launches the Gateway and the Web browser you haveselected. The setting is replaced with about: blank, which specifiesthat your home page will be a blank HTML page.

Type the URL and Navigate the Web Application for which youwanted to perform Load Test.

After you have completed the browser session, either close thebrowser window to end the recording, or switch back to ScriptModeler and click the Stop button , in the Capture/Replay Toolbar.


14/28

When you have finished recording the Script

the SCL formatted data is displayed in the

Script Pane as illustrated below:


15/28

Before you save your new Script you need tocompile it using the Syntax Check option toensure the validity of the recording.

Select Capture > Syntax Check or click , in theCapture/Replay Toolbar. Compilation results arereported in the Output Pane. If compilation is

unsuccessful, you may need to re-record theScript or model the contents to resolve theproblem.


16/28

After compilation replay the Script to check

the activity you have recorded. Select Capture

> Replay or click , in the Capture/Replay

Toolbar.

When you have finished recording, click , in

the Standard Toolbar to save your Script in the

Repository, or click File > Save.


17/28

Query Result Pane

After you have finished recording you can also view the HTML informationrecorded at the same time as the Script. You can access this data byopening a Script in Script Modeler then selecting a URL you want to viewfrom the URL Address Bar and clicking the URL Details button , in theStandard Toolbar. HTML information is organized into five categories:

HTML: Shows a browser view of the HTML document that has been

retrieved. Structure: Shows the basic elements of the page in a collapsing tree view.

DOM: Shows the page structure in the Document Object Model, as acollapsing tree view.

Server Header: Shows the HTTP response headers that the Web serverreturned to the browser.

Client Header: Shows the HTTP request headers provided by the browserfor the Web server.


18/28

Collectors

A Collector is a set of user-defined data collectionqueries which determine the type ofperformance data that is monitored and recorded

from one or more Host computers or devicesduring a Test-run.

Include Collectors in the Tests to target specificcomponents of the WAE under test and the Hosts

used to run a Test, with precise data collectionqueries to record the performance data youneed.


19/28

OpenSTA also supports the creation of Collector-only production monitoring Tests. These Tests areused to monitor and collect performance data

within a production system where the load isgenerated externally by the normal use of thesystem.

OpenSTA supplies two Modules which facilitate

the creation of Collectors: NT Performance Module

SNMP Module


20/28

NT Collectors

NT Performance Collectors are used tomonitor and collect performance data fromyour computer or other networked Hosts.

Use NT Performance Collectors to collectperformance data during a Test-run fromperformance objects such as Processor,Memory, Cache, Thread and Process on theHosts you specify in the data collectionqueries.


21/28

ow

Each performance object has an associated

set of performance counters that provideinformation about device usage, queue

lengths, delays, and information used to

measure throughput and internal congestion

as shown in fig.


22/28

Creating NT performance Collector

In Commander, select File > New Collector > NTPerformance.

Or: In the Repository Window, right-click Collectors,and select New Collector > NT Performance.

The Edit Query dialog box opens automatically whenyou open a new Collector. Use this dialog box to addNT Performance data collection queries.

Click the Browse Queries button to open the BrowsePerformance Counters dialog box and define thequery.


23/28

Creating a Test

After you have planned your Test use Commander tocoordinate the Test development process by selectingthe Scripts and Collectors you need and combiningthem into a new Test with the required Task Group

settings applied.In Commander select File > New Test > Tests.

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


24/28

Task Group Settings

Schedule Settings: Control when a Task Group starts and stops todetermine the period of data collection during a Test-run.

Host Settings: Specify the Host computer used to execute a TaskGroup during a Test-run. The Host computers you use can be local

Hosts on your Test network or remote, Web-based Hosts. For moreinformation see Running a Test Over the Web.

Virtual User Settings: Control the load generated against targetWAEs during a Test-run.

Task Settings: Control the number of times a Script is run and thedelay you may want to apply between each iteration of a Scriptduring a Test-run. You can also specify the type of delay, betweeneach Script iteration, which can be either Fixed or Random.


25/28

Test Pane

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

Repository Window. Use the Test Pane to create and edit a Test,

then apply the Task Group settings you requireto control how they behave during a Test-run.Run and monitor the Test-run then displayyour results for analysis.


26/28

The Test Pane comprises three sections

represented by the following tabs:

Configuration

Monitoring

Results


27/28

Running Test

Running a Test enables you to simulate real

end user Web activity and to generate the

results data you need in order to analyze and

assess the performance of target WAEs.

Start Test button Test-Pane toolbar .


28/28

Monitoring a Test-run

A summary of current Test-run activity.

Script-based Task Groups: All the Scripts in aTask Group and the Virtual Users currently

running each Script.

Collector-based Task Groups: All the data

collection queries defined in a Collector.

open sta info -final.pptx

Documents