Why do performance testing
2.
Activity 2. Identify Performance Acceptance Criteria. Identify the response time,
throughput, and resource utilization goals and constraints. In general, response time is
a user concern, throughput is a business concern, and resource utilization is a system
concern. Additionally, identify project success criteria that may not be captured by
those goals and constraints; for example, using performance tests to evaluate what
combination of configuration settings will result in the most desirable performance
characteristics.
3.
Activity 3. Plan and Design Tests. Identify key scenarios, determine variability
among representative users and how to simulate that variability, define test data, and
establish metrics to be collected. Consolidate this information into one or more
models of system usage to be implemented, executed, and analyzed.
4.
Activity 4. Configure the Test Environment. Prepare the test environment, tools,
and resources necessary to execute each strategy as features and components become
available for test. Ensure that the test environment is instrumented for resource
monitoring as necessary.
5.
Activity 5. Implement the Test Design. Develop the performance tests in
accordance with the test design.
6.
Activity 6. Execute the Test. Run and monitor your tests. Validate the tests, test
data, and results collection. Execute validated tests for analysis while monitoring the
test and the test environment.
7.
Activity 7. Analyze Results, Report, and Retest. Consolidate and share results
data. Analyze the data both individually and as a cross-functional team. Reprioritize
the remaining tests and re-execute them as needed. When all of the metric values are
within accepted limits, none of the set thresholds have been violated, and all of the
desired information has been collected, you have finished testing that particular
scenario on that particular configuration.
Why Do Performance Testing?
At the highest level, performance testing is almost always conducted to address one or
more risks related to expense, opportunity costs, continuity, and/or corporate reputation.
Some more specific reasons for conducting performance testing include:
·
Assessing release readiness by:
o
Enabling you to predict or estimate the performance characteristics of an
application in production and evaluate whether or not to address performance
concerns based on those predictions. These predictions are also valuable to the
stakeholders who make decisions about whether an application is ready for
release or capable of handling future growth, or whether it requires a
performance improvement/hardware upgrade prior to release.
o
Providing data indicating the likelihood of user dissatisfaction with the
performance characteristics of the system.
o
Providing data to aid in the prediction of revenue losses or damaged brand
credibility due to scalability or stability issues, or due to users being
dissatisfied with application response time.
·
Assessing infrastructure adequacy by:
o
Evaluating the adequacy of current capacity.
o
Determining the acceptability of stability.