01_Performance Testing Training

8/3/2019 01_Performance Testing Training

http://slidepdf.com/reader/full/01performance-testing-training 1/34

PERFORMANCE TESTING TRAINING

2008



SESSION 1 – OVERVIEW OF PERFORMANCE TESTING



| Financial Services

© 2008 Capgemini - All rights reserved 2

AGENDA FOR SESSION 1

Testing

Types of Testing

Performance Testing

What

Why

When

Objectives

Advantages & Disadvantages

Do’s & Don’ts

Steps/Phases

Terminology

Execution Models

Types

Various Tools





TESTING

Final stage of Software life cycle before going live

Stages in Software Life Cycle

• System/Information Engineering and Modeling

• Software Requirements Analysis

• System Analysis and Design

• Code Generation

• Testing

• Maintenance (Live and Post Live)





TYPES OF TESTING

Functional Testing

Performance Testing





FUNCTIONAL TESTING

Determines whether a product functions correctly according to itsspecifications and relevant documentation standards

Re-execution of one or more tests in subsequent build of the

application/product to ensure

• Revisiting and testing all prior bug-fixes in response to a new fix/enhancement

• Re-testing all programs that might be affected by the fix/enhancement

• Hidden Bugs are uncovered





PERFORMANCE TESTING

“Performance testing is the process by which software is tested to determine the

current system performance.”

Primarily used for…

determining capacity of existing systems.

creating benchmarks for future systems.

evaluating degradation with various loads and/or configurations.





FUNCTIONAL VS PERFORMANCE TESTING

Objective Example

Stability Will 2,000 concurrent hits crash the server?

Performance Is response time acceptable according to specifications?

Functionality under load Do business transactions function properly under heavy load?

Objective Example

Functionality Do business transactions function properly after implementation?

Functional

Performance





WHAT IS PERFORMANCE TESTING

A way of measuring the performance of your website/application

Process of simulating and analyzing the effect of many users on an application

Emulates user activity

Analyzes the effect of the real-world user environment on an application

Most effective way to gauge a Web site’s capacity and scalability





WHY PERFORMANCE TESTING

Speed

Does the application respond quickly enough for the intended users?

Scalability/Capacity

Will the application handle the expected user load and beyond?

Stability/Robustness

Is the application stable under expected and unexpected user loads?

Confidence

Are you sure that users will have a positive experience on go-live day?





WHY PERFORMANCE TESTING (contd)

Factors influencing Speed

User Expectations

Experience

Psychology

Usage

System Constraints

Hardware

Network

Software

Costs

Speed can be expensive!






SCALABILITY

How many users…

before it gets “slow”?

before it stops working?

Will it sustain?

do I expect today?

do I expect before the next upgrade?

How much data can it hold?

Database capacity

File Server capacity

Back-up Server capacity

Data growth rates






STABILITY

What happens if…

there are more users than we expect?

all the users do the same thing?

a user gets disconnected?

there is a Denial of Service Attack?

the web server goes down?

we get too many orders for the same thing?






CONFIDENCE

If you know what the performance is…

you can assess risk

you can make informed decisions

you can plan for the future

you can sleep the night before go-live day

The peace of mind that it will work on go-live day alone justifies the cost ofperformance testing





WHEN PERFORMANCE TESTING

Performance testing Process has to be:

Performed from Development stage to Pre-Production stage

Performed after the application has undergone functional testing to avoid

functional errors during load testing





OBJECTIVES

Application response time

How long does it take to complete a task?

Configuration sizing

Which configuration provides the bestperformance level?

Acceptance

Is the system stable enough to go into

production?Regression

Does the new version of the softwareadversely affect response time?

Reliability

How stable is the system under a heavywork load?

Capacity planning

At what point does degradation inperformance occur?

Bottleneck identification

What is the cause of degradation inperformance?

Product evaluation

What is the best server for 100 users?





ADVANTAGES

Helps to detect hidden bottlenecks or performance problems

Helps to predict how the site will function in the real world

Measures the end user response time for each transaction and user load level

Increases customer satisfaction and retention

Avoid project failures by predicting site behavior under large user loads





DISADVANTAGES

Performance tests that don’t simulate real scenarios can be dangerouslymisleading

Performance tests are just simulation but not realistic





DO’S

Do test early and do test often

Do establish what is and is not acceptable performance for your application

Do test from the user’s perspective - it’s the only one that counts

Do baseline and compare your findings

Do monitor your system while you test

Do test whenever there’s a change in your site’s content, code or infrastructure





DONT’S

Don’t wait until the last minute to test

Don’t depend on your customers to do your testing for you

Don’t test under unrealistic conditions

Don’t forget that increases in table sizes, disk usage and network traffic will

degrade your application’s performance over time

Don’t be so quick to throw hardware at the problems you turn up - it doesn’talways help





STEPS/PHASES





TERMINOLOGY

Time

User starts

requestUser finishes

request

System starts exec

System starts response

Response complete

Next user Request

Reaction Time

Response Time

(Defn. 1)

Response Time(Defn. 2)

Think Time





TERMINOLOGY

Virtual User: Software process that simulates real user interactions with the Application Under

Test (AUT)Navigation Flow: A user function within the Application Under Test

Scenario: A set of navigation flow defined for a set of virtual users to execute.

Think Time: Time taken by the user between page clicks

Ramp up: Gradual increase of vusers during controller execution

Throughput: It is the amount of work that a computer can do in a given time period

Transaction A subsection of the measured workflow

More granular user events for which response time will be measured

Bottleneck

A load point at which the System Under Test (SUT) /AUT suffers significant degradation

Breakpoint: A load point at which the SUT/AUT suffers degradation to the point of malfunction

Scalability The relative ability or inability of the AUT/SUT to produce consistent measurements

regardless of size of workload

Response Time: The time elapsed between when a request is made and when that request isfulfilled





EXECUTION MODELS

1. Over the netRemote execution of

performance tests from

offshore using remote

connectivity

2. Moving Labs

Generation of load fromcustomer site or hosting

data center

3. Replica at Lab

Implementation of pre-

production burn @CAPGEMINI Test Lab

Execution Models tailored to match client requirements





TYPES OF PERFORMANCE TESTING





TYPES OF PERFORMANCE TESTING (contd..)

Load Testing

Testing the service level when put under real world volumes of data

Stress Testing

Testing the maximum load of transaction/users that can be handled until breakdown point

Spike Testing

Testing by suddenly increasing the number of concurrent users logged on, to determine

the server behavior

Endurance Testing

To find problems that grow over a period of time, during continuous repetitive

transactions

Volume testing

Handling large amount of data





LOAD TESTING

Test: Determine if an application can meet a desired service level

under real world volumes





STRESS TESTING

Test: Determine the maximum load (typically number of concurrent

users/transaction) that the application can service i.e. the application’sbreaking point





ENDURANCE TESTING

Test: Subject an application to a pre-defined set of transaction scenario

continuously and repetitively for an extended period of time to find out thesmall problems that grow over a period of time (e.g. memory leaks)





SPIKE TESTING

Test: Simulate a sudden increase in the number of concurrent users

performing a specific transaction to determine the server behavior underabnormal traffic conditions





POPULAR PERFORMANCE TEST TOOLS

HP’s LoadRunner/ Performance Center

Segue’s SilkPerformer

Radview’s WebLoad

Empirix’s E-Test Suite Rational Robot

Compuware’s QALoad

Cynaro’s OpenSTA(OpenSource Tool)





COMPARISON OF TOOLS



www.capgemini.com/financialservices

Thanks and Good Luck

01_Performance Testing Training

Documents

Transcript of 01_Performance Testing Training