This document discusses performance testing of applications. It defines performance testing and describes different types of performance testing tools that can be used for testing applications from the client or server side. It emphasizes the importance of performance testing to ensure applications can handle expected user loads and transactions and provide positive user experiences. Key goals of performance testing are to test response times, speed, resource usage, stability, and throughput under different loads. Examples are provided of how performance issues negatively impacted major companies through lost revenue and customers.

2.  Functional and Performance
Testing.
 Why Performance
 Definitions
 Performance Testing Tools

3. Client Side
Records each user action
Only one User
Tool :QTP,Selenium
Server Side
Records only client –side interaction
Multiple User
Tool: Load Runner, Jmeter, Neoload

4. Why Performance…?
• Does the application respond
quickly enough for the intended
users?
• Will the application handle the
expected user load and beyond?
• Will the application handle the
number of transactions required by
the business?
• Is the application stable under
expected and unexpected user
loads?
• Are you sure that users will have a
positive experience on go-live day?

5. Goal of Performance
Performance
Test
Response
Time
Speed
Resource
Usage
Stability Throughput

6. Performance Life Cycle

7. Performance failure = Lost revenue
Amazon Inc US website was down for
about 2 hours
Impact : Amazon Shares fell 4.59
percent
Australia's JetStar airline website crashed as too many
users went online to take advantage of holiday
promotions.
Internet Business News: July 27,2006
Yahoo News : Fri Jun 6, 2008 4:50 PM ET

8.  Security flaw breached rules on confidentiality and data protection, and forced system
downtime, undermining campaign to win citizen confidence in online filing.
 In May 2002, 10 months after its launch, the Inland Revenue's self-assessment online
tax returns service suffered a major security breach
Failed to cope with expected surge in activity, resulting in forced downtime and extensive loss
of revenue. On 17 June 2002, the online betting site suffered an embarrassing outage two days
before the England versus Brazil World Cup game. The site was only offline for a day, but it
resulted in extensive revenue loss, and the loss of customers to other betting sites during what
was arguably the biggest betting event in a dozen years.

9. Egg.com (www.egg.com)
Upgrade/hardware crash triggered an outage; in the
aftermath the already slow systems could not cope with
reactivity.
For a whole week in January 2001, the pioneering online
banking service at egg.com simply disappeared.
Customers could access front-end information, but were
blocked from getting to the secure servers that held their
accounts. Only one explanation emerged: Egg's
developers had to take the site down while an upgrade
was underway to add support for interactive TV. That
was later modified to simply "a hardware problem".

11. Stress Testing: Stress Testing is done in order to check when the
application fails by varying the system resources such as RAM,
HDD etc. and keeping the number of users as constant.
Load Testing: Load Testing is done in order to check when the
application fails by increasing the number of users and keeping the
system resources as constant.
Performance Testing: The term Performance can mean
measuring response time, number of hits , resource utilization, or
some other system characteristic( or group of them), by varying
the number of users.