Performance

Only available on StudyMode
  • Download(s) : 32
  • Published : January 1, 2013
Open Document
Text Preview
Agenda
• Why Performance Testing? • Performance Testing Workflow • HP LoadRunner Solutions

2

Why Load Test Your Application?
Prevents costly failures of mission-critical applications. Assures performance and functionality under realworld conditions. Locates potential problems before your customers do. Reduces development time. Reduces infrastructure costs. 3

Types of Performance Testing

4

Examples of Performance Test Objectives
Application response time
• How long does it take to complete a task?

Reliability
• How stable is the system under a heavy work load?

Capacity planning Configuration sizing
• Which configuration provides the best performance level? • At what point does performance degradation occur?

Regression
• Does a new version of the software adversely affect response time? 5

Bottleneck identification
• What is the cause of the performance degrading?

Performance Testing Expert Workflow
• Establish Goals • Gather System Usage Information • Analyze System Under Test

6

GOALS

Defining Goals

Why

start with conceptual goals?
Conceptual goals should outline all of your load test objectives.

Examples of conceptual goals:




A high-priority example is the responsiveness of a “Search” function. Are we able to get search results within a reasonable time? A second example is the system administrator’s concern that the “Update” transaction functions during heaving usage.

In the initial stages, jotting down goals that can’t be measured will allow later filtering to create more focused goals. 7

GOALS

Quantifying Load Testing Goals

8

GATHERING INFORMATION

Gathering System Usage Information

Why gather system usage information?
Allows you to:
• Decide which business processes to test. • Isolate peak loads and peak load times. • Document user actions and valid input data for each

business process.

Where can we get information?
• Using the site, first-hand • Consulting with administrators • Consulting with executives • Researching competitor’s sites

9

GATHERING DATA

Obtaining Customer Locations

10

ANALYZING SYSTEM

Analyzing the System Under Test

Why gather system usage information?
• Allows you to setup monitors. • Allows you to effectively coordinate with backend experts. • Provides system information that helps isolate performance

problems.

Where can we get information?
• System Administrators • Backend experts • Application experts • Database Administrators

11

BUSINESS PROCESSES

Identifying Business Processes to Test
Mission-Critical Business Process
• Business Processes that are crucial in day-to-day

operations.

Heavy Throughput
• Heavy throughput business processes may not be mission-

critical but are very popular.

Dynamic Content
• Dynamic content consists of sever requests that are

customized for each user.

12

BUSINESS PROCESSES

Business Processes to Test: Mission-Critical Transactions

13

BUSINESS PROCESSES

Business Processes to Test: Heavy Throughput

14

BUSINESS PROCESSES

Business Processes to Test: Dynamic Content

15

BUSINESS PROCESSES

Business Process Profile

Business Typical Process Day Name
Sign in Create new account Search for flights View flight booking Purchase ticket 70/hr 10/hr 130/hr 20/hr 40/hr

Peak day

Dynamic content
Light Moderate Moderate Moderate Heavy

Mission critical
High Low Moderate High High

Test

210/hr 15/hr 180/hr 30/hr 90/hr

? ? ? ? ?

16

DOCUMENTATION

Documenting User Steps and Input Data

17

DOCUMENTATION

Determining Valid Test Data to Use

18

DOCUMENTATION

Valid Test Data Sources
Valid input data comes from three sources: Master Data
• Also known as Application Data • Data is resident in the application’s database – Examples: ID numbers and passwords

User-Generated Data
• Originates with the user – Examples: new unique ID or email address...
tracking img