This document discusses performance, acceptance, and stress testing. It defines each type of testing and outlines the typical processes involved. Performance testing checks a system's speed, scalability, and stability under varying loads without attempting to find bugs. Stress testing evaluates a system's robustness and error handling under extreme loads. Acceptance testing determines if a system meets requirements specifications before user acceptance.

1. Performance, Acceptance
and Stress Testing
Group Members
Ajay kumar
Nitin Sharma
Sidharth Rathore

2. Performance Testing
Performance Testing is a type of testing to ensure software applications will
perform well under their expected workload.
Features and Functionality supported by a software system is not the only concern.
A software application's performance like its response time, reliability, resource
usage and scalability do matter. The goal of Performance Testing is not to find bugs
but to eliminate performance bottlenecks.
The focus of Performance Testing is checking a software program's

3. Speed - Determines whether the application responds quickly
Scalability - Determines maximum user load the software application
can handle.
Stability - Determines if the application is stable under varying loads

4. Performance Testing Process
Below is a generic performance
testing process

5. 1. Identify your testing environment - Know your physical test
environment, production environment and what testing tools are
available. Understand details of the hardware, software and network
configurations used during testing before you begin the testing process.
It will help testers create more efficient tests.
2. Identify the performance acceptance criteria - This includes goals
and constraints for throughput, response times and resource
allocation. It is also necessary to identify project success criteria
outside of these goals and constraints.

6. 3. Plan & design performance tests - Determine how usage is likely to vary
amongst end users and identify key scenarios to test for all possible use cases. It
is necessary to simulate a variety of end users, plan performance test data and
outline what metrics will be gathered.
4. Configuring the test environment - Prepare the testing environment before
execution. Also, arrange tools and other resources.
5. Implement test design - Create the performance tests according to your test
design.
6. Run the tests - Execute and monitor the tests.
7. Analyze, tune and retest - Consolidate, analyze and share test results. Then
fine tune and test again to see if there is an improvement or decrease in
performance. Since improvements generally grow smaller with each retest, stop
when bottlenecking is caused by the CPU.

7. Performance Parameters Monitored

8. Stress Testing
Stress testing is used to test the
stability & reliability of the system. This
test mainly determines the system on
its robustness and error handling under
extremely heavy load conditions.
It even tests beyond the normal
operating point and evaluates how the
system works under those extreme
conditions. Stress Testing is done to
make sure that the system would not
crash under crunch situations.

9. Stress testing is also known as endurance testing. Under Stress Testing,
AUT is be stressed for a short period of time to know its withstanding
capacity. Most prominent use of stress testing is to determine the limit,
at which the system or software or hardware breaks. It also checks
whether system demonstrates effective error management under
extreme conditions.

10. Need for Stress Testing
During festival time, an online shopping site may witness a spike in
traffic, or when it announces a sale.
When a blog is mentioned in a leading newspaper, it experiences a
sudden surge in traffic.
It is imperative to perform Stress Testing to accommodate such
abnormal traffic spikes. Failure to accommodate this sudden traffic may
result in loss of revenue and repute.

11. Stress testing is also extremely valuable for the following reasons:
- To check whether the system works under abnormal conditions.
- Displaying appropriate error message when the system is under
stress.
- System failure under extreme conditions could result in enormous
revenue loss
- It is better to be prepared for extreme conditions by executing Stress
Testing.

12. Load Testing vs Stress Testing

13. Acceptance Testing
Acceptance testing, a testing technique performed to determine
whether or not the software system has met the requirement
specifications. The main purpose of this test is to evaluate the system's
compliance with the business requirements and verify if it is has met
the required criteria for delivery to end users.

14. Acceptance Testing - In SDLC
The acceptance test cases are executed against the test
data or using an acceptance test script and then the
results are compared with the expected ones.

15. Forms of Acceptance testing
-User acceptance Testing : the users test the software to make sure it can
handle required tasks in real-world scenarios, according to specifications.
-Business acceptance Testing : where the software test according to business
reqiurement.
-Alpha Testing: Alpha testing performed by Testers who are usually internal
employees of the organization
-Beta Testing: Beta testing is performed by Clients or End Users who are not
employees of the organization

16. Acceptance Criteria
-Functional Correctness and Completeness
-Data Integrity
-Data Conversion
-Usability
-Performance
-Timeliness
-Confidentiality and Availability
-Installability and Upgradability
-Scalability
-Documentation

17. The Acceptance test plan has the following
attributes:
Introduction
Acceptance Test Category
operation Environment
Test case ID
Test Title
Test Objective
Test Procedure
Test Schedule
Resources

18. Acceptance Test Plan - Attributes
The acceptance test activities are carried out in phases. Firstly, the
basic tests are executed, and if the test results are satisfactory then the
execution of more complex scenarios are carried out.