Definition of Performance Testing:
Quality Assurance stands for software performance testing. This testing confirm performance of software applications under the expected and required pressure or workload..
The main motive of performance testing is to eliminate the
performance bottlenecks instead of finding the bug in application. Performance
testing mean ability to response, and response time.
Following Three Points need to keep in mind during
Performance Testing:
Speed – Application responds should quick
Scalability – How many users can access the website
at once.
Stability – How much loads can be bear by any
software application.
Why performance testing is required:
This testing uncovers those general requirements which
should be implementing for all software application before launching the live.
To confirm the speed, scalability and stability of software application we
perform the performance testing.
Following are the Types of Performance Testing:
i.
Load Testing: Need to check
the application under anticipated loads of users.
ii.
Stress Testing: Handling the
high traffic and data processing for application.
iii.
Endurance Testing: How long
and how much load application can handle.
iv.
Spike Testing: Tests the
software’s response to rapid large spikes in the load generated by visitors.
v.
Volume testing: Large amount
of data handling by software via database changes.
vi.
Scabalibility Testing: To
confirm the effectiveness of application and how it can be scale up to improve
the performance of application.
Some Common Performance Problems in Software Application:
are
i.
Long load time: Taking too
much time in loading the simple pages of website.
ii.
Poor Response Time: It is post
back condition, when user will submit query to server and server will reply
that query, If Time estimation of query and its response is too long then it
will called poor response time.
iii.
Poor Scalability – If
application can not bear the expected number of users then it comes in poor
scalability.
iv.
Bottlenecking – Due to any
coding error or hardware lack, when application fail for expected result then
it will called bottlenecking:
Some common performance
bottlenecks: are
a.
CPU Utilization
b.
Disk usage
c.
Memory utilization
d.
Operating System limitations
e.
Network Utilization
Performance Testing Process:
1. First Performance tester will identify the Testing Environment
which will most suitable for performance testing.
2. Now tester will Check and confirm the performance acceptance
criteria in which application will satisfy the acceptance requirement.
3. Now time to plan and design the performance test cases to
complete this testing.
4. Before start testing need to configure all required Test
environment.
5. Test design need to implement now.
6. Execute the Test Cases and creating the bug list report.
7. Need to Analyze, tune and retest the found bugs and fixes.
Monitored the Performance Parameters:
- How much usage of Processor.
- Usage of Memory
- Timing of disk
- Bandwidth record
- Private bytes usage
- Memory commitment
- Memory pages/second
- Pages faults per second
- CPU interrupts / second
- Length of Disk Queue
- Length of network output queue
- Network bytes total per second
- Response time
- Throughout the testing
- Connection pooling amount
- Active sessions on maximum level
- High Hit ratios
- Rollback segment
- Database locking
- Top waiting
- Thread counts
- Garbage collection
Performance Testing automation tools:
- HP Loadrunner
- HTTP Load
- Proxy Sniffer
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
Monitored and Types of and Definition of
Performance Testing, Performance Testing automation tools, real world
scenarios example for performance testing, process the Performance Parameters, Common
Performance Problems in Software Application or website ..
No comments:
Post a Comment