background image
<< Using this guide | The performance-testing approach >>
<< Using this guide | The performance-testing approach >>

Chapters of this guide


Part II, Exemplar Performance Testing Approaches
·
Chapter 4 ­ Web Application Performance Testing Core Activities
·
Chapter 5 ­ Coordinating Performance Testing with an Iteration-Based Process
·
Chapter 6 ­ Managing an Agile Performance Test Cycle
·
Chapter 7 ­ Managing the Performance Test Cycle in a Regulated (CMMI)
Environment

Part III, Identify the Test Environment
·
Chapter 8 ­ Evaluating Systems to Increase Performance-Testing Effectiveness

Part IV, Identify Performance Acceptance Criteria
·
Chapter 9 ­ Determining Performance Testing Objectives
·
Chapter 10 ­ Quantifying End-User Response Time Goals
·
Chapter 11 ­ Consolidating Various Types of Performance Acceptance Criteria

Part V, Plan and Design Tests
·
Chapter 12 ­ Modeling Application Usage
·
Chapter 13 ­ Determining Individual User Data and Variances

Part VI, Execute Tests
·
Chapter 14 ­ Test Execution

Part VII, Analyze Results and Report
·
Chapter 15 ­ Key Mathematic Principles for Performance Testers
·
Chapter 16 ­ Performance Test Reporting Fundamentals

Part VIII, Performance-Testing Techniques
·
Chapter 17 ­ Load-Testing Web Applications
·
Chapter 18 ­ Stress-Testing Web Applications
Approach Used in This Guide
The primary task of any testing activity is to collect information in order to be able to
help stakeholders make informed decisions related to the overall quality of the
application being tested. Performance testing additionally tends to focus on helping to
identify bottlenecks in a system, tuning a system, establishing a baseline for future
testing, and determining compliance with performance goals and requirements. In
addition, the results from performance testing and analysis can help you to estimate the
hardware configuration required to support the application(s) when you "go live" to
production operation.