IBM Software Group

Rational Performance Tester Introduction

Rational Performance Tester: Overview

Multi-user automated performance testing tool for Webbased applications

Hosted in the IBM Rational Software Development

Platform (RSDP), a version of the Eclipse shell

RPTs tests and execution engine based on the Java

programming language

Highly scalable Platform support

o Record and test execution on Windows and Linux o Agents (test execution) on some additional Windows Server platforms

Rational Performance Tester: Architecture

Built on top of the IBM Rational Software

Development Platform (RSDP), TPTP, and custom components

IBM Rational Performance Tester (RPT)

Eclipse Test and Performance Tools Platform (TPTP)

IBM Rational Software Development Platform (RSDP)

IBM Rational Software Development Platform (RSDP)

Workbench - The user interface and integrated

development environment (IDE) in Eclipse and in the Rational Developer products, which are based on Eclipse.

Powered by Eclipse Technology

Workspace - In Eclipse, the collection of projects

and other resources that the user is currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might reside in the same directory.

Relationship of the Workbench and Workspace

WORKSPACE
Folders
Workbenc h

Project

Test Assets Suppo

rt Files

Specify a Workspace to run the Workbench

Workbenc h

Eclipse Test and Performance Tools Platform (TPTP) Test Perspective - Common set of views and editors
toolset

HTTP Proxy Recorder - Test capture and generation Execution framework - Test suites, deployments and
locations

Agent Controller - A daemon process that resides on

each deployment host and provides the mechanism by which client applications either launch new host processes or attach to agents that coexist within existing processes on the host

Reporting framework

Test Perspective: Default Layout

Perspective Indicators Display area for: Test Editor Schedule Editor Real-time test run stats Test Execution History Report Viewer

Hierarchical project browser Default Views

Rational Performance Tester: Features

HTTP and HTTPS protocol support and capture Graphical test editing and workload modeling Built-in Verification Points (VPs) Data substitution with datapools Real-time monitoring and reporting Report customization and export capability Programming extensibility with Java custom code

RPT and the Performance Testing Framework (PTF)

Test Planning and Design
Performance Test Plan Workload Analysis

Test Development and Validation

Record Transactions Modify Tests Design Workloads Validate and Debug Tests

IBM Rational Performance Tester

Test Lab Hardware System Software Data Set Test and Monitoring Tools Reset System and Data StateRun Monitoring Tools Run Tests Evaluate Results Tests and Execute

Set up Test Environment

Gather Measurements

Rational Performance Tester: Test Development

Test editor

Project and file browser

Protocol Data view

Rational Performance Tester: Workload Design

Schedule editor

Schedule Run Settings

Schedule

Rational Performance Tester: Test Execution

Run-Time Test Control

Change Log

Level Add Virtual Users Stop Test Run

Rational Performance Tester: Test Monitoring

Default Real-Time Reports

Rational Performance Tester: Results Analysis

Execution History

Log of Events

Reports

Key Terms

View - In Eclipse-based user interfaces, any pane in the

workbench that is outside the editor area and can be stacked (dragged and dropped) on top of other views. Views provide different ways to look at or work with the resources in the workbench.

Perspective - A group of views that show various aspects of

the resources in the workbench. The workbench user can switch perspectives, depending on the task at hand, and customize the layout of views and editors within the perspective.

Projects - In Eclipse, a unit of organization used to group

folders or packages. Projects are used for building, version management, sharing, and organizing resources.

Views Contained within the Test Perspective Test-related Views

o Test Navigator

o Recorder Control
o Protocol Data o Performance Test Runs
Customize your perspective close views to minimize clutter

Editor and Viewer area

Other Views
o Properties
o Tasks (rarely used) o Outline (not used)

Editors and Viewers

o Test and Schedule Editors o Report and History Viewers

Other Perspectives and Views

Perspectives
o Java

Navigator View exposes file extensions and hidden files

o Resource

Views
o Navigator
Helpful to add this view to the Test Perspective

Window > Show View > Other > Basic > Navigator

o Package Explorer

Working with Perspectives

Window > Open Perspective Switch between open Perspectives using the shortcut bar Manage Perspectives

Reset to restore

Managing Perspectives

Or click Other

Perspective Shortcut Bar

Working with Views

Window > Show View Customize the layout of your views

o Group, dock, and layer using drag and drop o Minimize, maximize, and resize

o Show, close, move to Fast View

Min/Max

Resize Or click Other

Fast View Toolbar An alternative to closing views

is to move them to the Fast View toolbar.

Click an icon in the Fast View

toolbar to open the View.

Click anything else in the

Perspective to close the View.
To create a Fast View, click a view (tab), drag the view to the toolbar.

Fast View toolbar

Rational Performance Tester: Data Storage

Workspace
o Default location: C:\Documents and
Settings\user\IBM\rationalsdp6.0\workspace

o Maintains perspectives and view settings (.metadata)

Project
o Storage location for: Recordings (trace files)

Test Suites (Performance Tests and Schedules)

Test logs and results Datapools

Performance Test Project

Specialized Java project

o Specific directory structure for housing and running RPT tests o Template provided out-of-the-box for manual creation o Auto-created on first record if no project exists Default name: testproj

Projects can reside inside the Eclipse Workspace

or in another location

Create a Performance Test Project Manually File > New > Performance Test Project

Create a Performance Test Project Creates a Java project Manually (cont.) customized for performance

By default, it is created in

testing

Project name cannot

include
o/ \ * : < > | ?

the Eclipse workspace

o Names ending with a period

Test Navigator View: Project and File Management Project browser tool
o Create and browse objects o Open or close projects o Delete objects
Default project structure

Functions enabled
using shortcut menu
o RPT specific
o Workbench tools

Filtered view

Test Navigator View: File Filtering

Shows only commonly

edited and viewed files such as:
o Performance Tests and Schedules

o Datapools
o Locations

Supporting files not shown Some directories appear

empty

Tip: File Management Using Views

Test Navigator view

Performance Test Runs

Navigator View exposes additional project files

filters many file types

only show test results files

Navigator View: Alternate File Browser

No filtering Test files

o Recordings (trace files) o Test and Schedules

o Source and compiled files

Report source files

o Raw test run data

Project files
o .classpath, and so on

Testproj Default Project: Directory Structure

Default location for all projects is the workspace directory

Testproj Default Project: Directory Structure Default (cont.)

o bin

Default Directory Structure

o src

Suggested
o Tests
o Schedules o Test Results o Datapools o Deployments or Locations
Suggested Directory Structure

Creating Folders

Test Navigator view; shortcut menu

o File > New > Folder

Workbench
menu
o File > New

> Folder

Specify
o Location o Name

Default Directory Structure and Test Before Test \bin \src Execution
Execution After Test Execution <no files> \bin\test <no files> \src\test

.class files

.java files

Test Navigator does not display test source or compiled files

Overall Page

It contains a progress
indicator and bar charts

The bar charts show

o Overall success of run o % Page element status code success o % Page status code success o Optionally, % Verification Points passed (Title, Page or Size)

Summary Report

It contains Run Summary,

Page Summary and Page Element summary

Each summary explains

o Run Status

o Duration
o Active/completed/total user o Max/Min/Avg response time

o Total Hits
o % VP passed

Page Performance

It contains two section i.e.

graph and table
o Avg. response time for each page

The table contains

o Min response time
o Avg. response time o Max response time

o No of attempts/Sec
o No. of total attempts

Response Vs Time Summary Report

It shows avg. response

time through time

It contains two line graphs

and related summary table
o One line graph shows the avg. response time for all page during the run o Other line graph shows the avg. response time for all page element during the run o The tables shows total avg. response time

Response Vs Time Details

It shows the response

It contains a graph and a

table
o Graph shows the avg. response of each page through time o Min. response time o Max response time

trend through time

o Avg. response time

o No of page attempts per interval o Rate of page attempts per interval

Page Throughput

It gives the overview of

the frequency of the requests being transferred per interval
o Page attempts rate and page hit rate per interval o Summary tables shows total hit rates and counts for each page

o Active and completed users over the course of run

o Summary table Sample interval

Server Health Summary Report

Overall indication about the

The bar charts (left)

o Page hits

server response to the user load

o Total Page attempts o Status code success o Total Page elements attempts o Page element hits

The bar chart (right)

The tables gives the same info

as the charts

o Page element status code success

Server Health Details

Provides specific details

about 10 least successful pages

The table contains

o No of attempts

o Hits
o Success o Attempts per second

Transaction Report Overall

Contains a line graph and

summary table

Line graph shows avg.

execution time for all transaction within interval

The table shows

o Avg. execution time o Std deviation of the avg. response time o Longest transaction o Shortest transaction

Transaction Report Duration Vs Time

Avg. response time of

each transaction during an interval

The table contains

o Min execution time o Avg. execution time o Std deviation of avg. response time

o Max execution time

o Rate per second o No. of attempts

Transaction Report Transaction Throughput Page Overview of the transaction

Graph (left) overall rates for

Table (left) shows
starting and completing transaction during interval
o Transaction rate per sec

frequency and the no of user adding load over the run

Graph (right) no of active and Table contains

o Active user o Completed user

o No of transaction

completed user over the course

o Total users

Verification Point Report

Summary (Graph and Table)

o % verification point passed per interval

Page verification Point (Table)

o No of VP passed o No of VP failed

o % of VP passed

Page Element Verification Point (Table)

o No of page and element o No of VP passed o No of VP failed o % of VP passed

Resource Monitoring

Used to capture data such as CPU usage, Memory etc. Comprehensive view of a system to aid in problem
determination

Can be done by
o Test agent

o Tivoli Monitoring agent

o Windows Performance Monitor o UNIX rstatd monitor

How to perform
o Enabling resource monitoring o Adding resource monitoring data source

Resource Monitoring Enabling

Enabling resource monitoring

o Enable resource monitoring from scheduler tab

Adding resource monitoring data source

o Configure the time interval

o Configure the counters

View report
o A separate tab generated with the details log

Performance Scheduler

General Run Duration Think Time Resource Monitoring Statistics Test Log Response time Break down Problem Determination

Response Time BreakDown

Response time breakdown lets you drill down into

the response time statistics on any HTTP page element.

The statistics show how much time was spent in

each part of the system under test.

Which application on which server is the

performance bottleneck, and then drill down further

to determine exactly which package, class, or

method is causing the problem.