The following are the types of testings.
1. Warm up test/Dry-run test/Discovery test:
This is not the actual test but making ensure that all scripts, test data, environment and
application running fine and stable.
Note: Warm up test will conduct with 10% or 100% of actual load for short duration.
2. Performance test/Baseline test:
Whenever you don’t have SLAs, you have to conduct baseline test with single user, single script, single iteration and execute the script in standalone mode and get the response times, consider as a baseline response time.
Step 1: Choose schedule by group option
Step 2: Choose start scenario begin option to make scripts run one by one.
Note: Application should behave properly under the load how it was behaved with a single user.
3. Load Test:
Load testing is the testing to verify the application behaviour under load.
We are designing the scenario with 100% load.
4. Endurance Test/Soak Test/Longitivity Test:
Verifying whether application is available for longer duration or not.
We have to design endurance test with normal load (50-60% of peak load) for longer duration (12h, 18h, 24h)
Note 1: Objective of this test is to identify the memory leakages.
Note 2: In some cases, we might require to design scenario with normal load by increasing think time and pacing time.
5. Stress Test:
Stress test is the test to identify the breaking point or performance degradation point of
application.
We can stress the application in two ways:
1. By increasing the number of users
2. By reducing the pacing and think time
Note: We can increase the number of transactions by reducing the pacing and think time without adding the users.
6. Failover Test (based on client request):
In the absence of first data cord, verifying whether second data cord can take the load without any failure transactions or performance degradation.
Process:
In one of my test, we designed a failover test for 2 hours duration. After one hour duration, we reported to IT admin and architect people to unplug the first data cord from the network. We verified whether test reported any failure transactions or performance degradations. Monitored second data cord whether it is able to take entire load in the absence of first data cord.
In the above scenario, my role is very minimal. Plugging and unplugging performed by network people.
7. Benchmark Test:
Benchmark test will give a repeatable set of quantifiable results which from current and future releases. These results has to be compared with baseline test results.
8. Capacity Planning Test:
By forecasting the future usage, whatever the sequence of test we are conducting is called capacity planning test.
Process:
We have to conduct load test, stress test to identify application breaking point. Speak with BA people to understand what is the growth of the business and plan for capacity planning.
9. Spike Test:
We have to test the application behavior under abnormal conditions.
10. Volume Test:
Volume test is the test to verify the application behavior under huge amount of load.
Example: Interfaces and Batches
11. Scalability Test:
Scalability Test is the testing of an application to measure its capacity. Scale up or scale down using horizontal and vertical techniques.
We can scale down application in two ways:
1. Vertical scale down: Adding the resources to same node (CPU, memory,cores)
2. Horizontal scaling: We can add multiple nodes to existing system.
12. Network Latency/Wan Emulation Test:
To simulate the network latency (delay) we used HP Shunra (Network Virtualization) and conducting virtualization test.
Memory footprint test: Testing with single user or 20 users and 50 users conducting how many users it can sustain called memory footprint test.Current version of LR will send the notification whenever it reaches the threshold point.
Memory Foot Print in Load Generators:
The no of Load Generators depend on the below items.
1. Ram size of the Load Generator.
2. No of Variables & Memory allocation for variables in LR Script
3. How you are running vuser as a Process or a Thread.
If you are running vuser as a process
1 vuser process1 MDRV Engine5mb
If you are running vuser as a Thread
1 vuser (50) Thread1 MDRV Engine2mb
1. Warm up test/Dry-run test/Discovery test:
This is not the actual test but making ensure that all scripts, test data, environment and
application running fine and stable.
Note: Warm up test will conduct with 10% or 100% of actual load for short duration.
2. Performance test/Baseline test:
Whenever you don’t have SLAs, you have to conduct baseline test with single user, single script, single iteration and execute the script in standalone mode and get the response times, consider as a baseline response time.
Step 1: Choose schedule by group option
Step 2: Choose start scenario begin option to make scripts run one by one.
Note: Application should behave properly under the load how it was behaved with a single user.
3. Load Test:
Load testing is the testing to verify the application behaviour under load.
We are designing the scenario with 100% load.
4. Endurance Test/Soak Test/Longitivity Test:
Verifying whether application is available for longer duration or not.
We have to design endurance test with normal load (50-60% of peak load) for longer duration (12h, 18h, 24h)
Note 1: Objective of this test is to identify the memory leakages.
Note 2: In some cases, we might require to design scenario with normal load by increasing think time and pacing time.
5. Stress Test:
Stress test is the test to identify the breaking point or performance degradation point of
application.
We can stress the application in two ways:
1. By increasing the number of users
2. By reducing the pacing and think time
Note: We can increase the number of transactions by reducing the pacing and think time without adding the users.
6. Failover Test (based on client request):
In the absence of first data cord, verifying whether second data cord can take the load without any failure transactions or performance degradation.
Process:
In one of my test, we designed a failover test for 2 hours duration. After one hour duration, we reported to IT admin and architect people to unplug the first data cord from the network. We verified whether test reported any failure transactions or performance degradations. Monitored second data cord whether it is able to take entire load in the absence of first data cord.
In the above scenario, my role is very minimal. Plugging and unplugging performed by network people.
7. Benchmark Test:
Benchmark test will give a repeatable set of quantifiable results which from current and future releases. These results has to be compared with baseline test results.
8. Capacity Planning Test:
By forecasting the future usage, whatever the sequence of test we are conducting is called capacity planning test.
Process:
We have to conduct load test, stress test to identify application breaking point. Speak with BA people to understand what is the growth of the business and plan for capacity planning.
9. Spike Test:
We have to test the application behavior under abnormal conditions.
10. Volume Test:
Volume test is the test to verify the application behavior under huge amount of load.
Example: Interfaces and Batches
11. Scalability Test:
Scalability Test is the testing of an application to measure its capacity. Scale up or scale down using horizontal and vertical techniques.
We can scale down application in two ways:
1. Vertical scale down: Adding the resources to same node (CPU, memory,cores)
2. Horizontal scaling: We can add multiple nodes to existing system.
12. Network Latency/Wan Emulation Test:
To simulate the network latency (delay) we used HP Shunra (Network Virtualization) and conducting virtualization test.
Memory footprint test: Testing with single user or 20 users and 50 users conducting how many users it can sustain called memory footprint test.Current version of LR will send the notification whenever it reaches the threshold point.
Memory Foot Print in Load Generators:
The no of Load Generators depend on the below items.
1. Ram size of the Load Generator.
2. No of Variables & Memory allocation for variables in LR Script
3. How you are running vuser as a Process or a Thread.
If you are running vuser as a process
1 vuser process1 MDRV Engine5mb
If you are running vuser as a Thread
1 vuser (50) Thread1 MDRV Engine2mb
No comments:
Post a Comment