The basic purpose of this document is to give a high level introduction to Software Load and Performance testing methodologies and strategies. This document is intended to facilitate Software test Managers, Project Managers, Software Engineers, Test Leads, Test engineers, and QA leads — anyone who is responsible for planning and/or implementation of a successful and cost effective performance testing program.
 

Load testing is the process of subjecting a computer, peripheral, server, network or application to a work level approaching the limits of its specifications. Load testing can be done under controlled lab conditions to compare the capabilities of different systems or to accurately measure the capabilities of a single system. Load testing can also be done in the field to obtain a qualitative idea of how well a system functions in the "real world."

During a test session, virtual clients generate result data (metrics) as they run

scenarios against an application. These metrics determine the applicationÙs

performance, and provide specific information on system errors and individual

functions. Understanding these different metrics will enable you to match them to

the application function and build a more streamlined test plan. (The names may

differ, but the following metrics are provided by most of the popular testing

software.)

 

Performance testing in general terms is testing that is performed, from one perspective, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage. Performance testing is a subset of Performance Engineering, an emerging computer science practice that strives to build performance into the design and architecture of a system, prior to the onset of actual coding effort.

This final article in our three-part series on testing for performance looks at test execution and results reporting. As a reminder, the Testing for Performance series is broken into the following parts:

Assess the problem space: Understand your content, the system, and figure out where to start

Build out the test assets: Stage the environments, identify data, building out the scripts, and calibrate your tests

Provide information: Run your tests, analyze results, make them meaningful to the team, and work through the tuning process

As we look at the steps required to provide performance-related information, we will try to tie the artifacts and activities we use back to the work that...

In thissecond article of our three-part series on testing for performance we look atbuilding our test assets and the work required to support that effort. As areminder, the Testing for Performance series is broken into the followingparts:

     * Assess the problem space: Understandyour content, the system and figure out where to start

    * Build out the test assets: Stage theenvironments, identify data, building out the scripts and calibrate your tests

    * Provide information: Run your tests,analyze results, make them meaningful to the team and work through the  tuningprocess

 Aswe look at the various environments, tools...

Thisthree-part series of articles on testing for performance outlines how you mightapproach

performancetesting. The series is broken into the following articles which will be posted in coming days:

 

    * Assess the problem space: Understandyour content and the system, and figure out where to

      start

    * Build out the test assets: Stage theenvironments, identify data, build out the scripts, and

      calibrate your tests

    * Provide information: Run your tests,analyze results, make them meaningful to the team, and

      work through the tuning...

The purpose of this document is to explain how to go about performing scalability testing, performance testing, and optimization, in a typical Java 2 Enterprise Edition (J2EE) environment.  

<!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";}@page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;}div.Section1 {page:Section1;}-->

Features

Rational Performance Tester

Mercury LoadRunner

Straight-forward, easy to understand UI with tree-view of

Ok with this Point

Its very easy to learn.

test for novice and mid-level testers. Test details hidden





in UI but available for experienced...