Performance Tester Salary in India

How much does a performance tester/performance engineer earn in india based on their experience and expertise? if you reached this blog seeking the answer your direction is right! Let’s have a look at performance tester salaries in India.
Let us now look at the performance tester salary of employees at present vs average expected salary in various IT hubs in India.
Performance Tester Salary in Pune
After Mumbai Pune is the second-best tech hub in the state, Pune plays a pivotal role in the growth of the IT hub in Maharashtra.
The salary packages for performance testers vary based on the city and also the size or number of organizations in the area. There are several companies in Pune with excellent opportunities for performance testers.  There are more than 80+ companies are Pune that has performance testing as one of their major services.
Based on data gathered from performance testers, we are trying to compare the current as well as the expected salary of employees who are looking for a job change

Experience Current salary Expected salary
2-4 yrs 4-6 LPA 5-7 LPA
4-5 yrs 8-7 LPA 7-8 LPA
5-6+ yrs 7-9 LPA 10-12 LPA

Performance Tester Salary in Bangalore
Bangalore in our very own Silicon Valley, the biggest IT hub of the country. Bangalore has always been the favorite of IT-based employees owing to the salary package offered by the companies there. When it comes to performance tester salary story remains the same. Let’s have a look

Experience Current salary Expected salary
2-4 yrs 5.7-6.25 LPA 5.20-7.30 LPA
4-5 yrs 8.15-7.20 LPA 7-8 LPA
5-6+ yrs 7.5-9 LPA 10.5-12.5 LPA

 Performance Tester Salary in Chennai
Chennai is one of the fast-growing and one of the biggest IT hubs in South India. Today Chennai is home to many big companies and well-known IT parks of the country including Elcot SEZ, Tidel Park, MEPS, Ramanujan IT  Park, Mahindra World City, ASV Suntech Park, RMZ Millenia, and many more.
Chennai is the right place to be if you are a fresher. The place offers a decent package as well as a fertile ground for budding performance testers.  Let’s have a look at the salary disparities.

Experience Current salary Expected salary
2-4 yrs 5.1-5.25 LPA 5.3-6.30 LPA
4-5 yrs 6.75-7 LPA 7.2-8.3 LPA
5-6+ yrs 7.5-9 LPA 10.5-12.5 LPA

Performance Tester Salary in Hyderabad
Another upcoming IT hub of South India is Hyderabad which is locally also called Cyberabad for obvious reasons. There are many IT hubs created in the area for the promotions of IT Infrastructure.
At present Hyderabad is home to many well-known names in IT including Google, Microsoft, GE, Qualcomm, Facebook, Amazon, and more. This list itself speaks volumes of the opportunities available in the region for every IT professional.

Also Read: Salary of testers in various countries revealed

Let’s have a look at the current average salary employees are drawing vs the expected average salary of performance testers

Experience Current salary Expected salary
2-4 yrs 3.7-5.8 LPA 5-7 LPA
4-5 yrs 6.5-8 LPA 7-8 LPA
5-6+ yrs 7-9 LPA 8-10 LPA

Performance Tester Salary in Mumbai
Mumbai! the name says it all. It’s a known fact that Mumbai is indeed one of the most prominent tech hubs in India. The salary package offered by various companies dwindles drastically owing to the budget variances of the company located there. From MNCs and here is what we got to know from the survey we conducted from performance testers working in Mumbai.

Experience Current salary Expected salary
2-4 yrs 4.20 -5.8 LPA 5-6.5 LPA
4-5 yrs 6.05-7 LPA 6-7 LPA
5-6+ yrs 8-8.5 LPA 9-11 LPA

Hope the idea about performance tester salary in India is clear now.  It’s expected that the role of a performance tester to performance engineer will happen widely across the dev world soon.

What is Software Performance Testing?

Software performance testing checks the actual software with specifications mentioned before it is being built. Its most basic function is to work as a diagnostic aid to locate problems in communication. Scott Barber, a famous testing expert, said that it is difficult to pinpoint an exact definition for performance testing because it works differently in different situations and other various companies.

Software performance testing
What is software performance testing?
Usually, software performance testing is performed to validate and verify quality metrics of software such as robustness, reliability, scalability, etc.
The software will be subjected to various load conditions and its response and output will be measured to find out various factors.

Typed of software performance testing

However, every company uses different types of performance tests depending upon the testing environment. Here’s a look at some of the popular performance testing:

1. Load Testing

One of the most basic types of performance testing, load testing method checks the increasing load of the software until the threshold is reached. Increasing load means an increasing number of simultaneous users, transactions, and behavior of the software under test situations.

The testing’s primary purpose is to observe the response time to ensure that the software can withstand a certain amount of load at any given time, which is why it is also called Volume Testing.

2. Stress Testing

Stress testing is another common performance testing method that checks the stability of the software when hardware including CPU, disk space, and memory isn’t stable. It is negative testing in which software is loaded with a large number of concurrent users that can’t be handled by the software.

It is a type of non-functional testing because it tests the non-functional aspects of a website or application, which is carried under a controlled situation so that it can capture uncertain scenarios and rectify them.

3. Throttle Testing

Throttle testing is a limited testing situation in which a load is tested at a limited speed to check the speed at which a website will load for users who have low network connectivity including those living in distant areas, 3G and 2G data, and using mobile internet. This testing makes use of certain tools like traffic sharpers and speed stimulators.

4. Endurance Testing

In endurance testing, the software is tested with a fixed amount of load for a long period of time to observe the system’s behavior. For instance, if the software is designed to work properly for four hours, its endurance is to be tested for double the time, which is eight hours.

This type of performance testing is used to check if there are any system fails or memory leaks. Endurance testing is often referred to as soak testing.

5. Spike Testing

Spike testing is similar to stress testing but the software is tested against load volumes and workload models for a longer time with a simultaneous increase in concurrent load.

The test is conducted for a time longer than its anticipated functioning time. Any unknown behavior is tapped and corrected at the very moment.

6. Smoke Testing

In smoke testing, the software is run on a very small load, which is much less than it can usually handle. If the test generates smoke, then the software has an error in its script.

It is one of the simplest tests used and usually the verification test that is run before the software is launched or larger tests are run.

7. Capacity Testing

As simple as it sounds, a capacity test is one in which the software is tested for the load it takes handle at any given time. When you know how many users your software can handle, you have better visibility of future events that might limit your application or website. It is a confirmatory test to avoid any future problems especially when you want to increase the volume of data.

8. Component Testing

Component testing checks the functionality of a particular part of your application or website. It tests simple but important aspects including file upload, shopping cart, email function, chart feature, or search function.

9. Peak Testing

In peak testing, you expose the software with increased load for a small time and regular peak in concurrent users to analyze how the website or application will behave in a real-life situations.

10. Scalability Testing

This kind of performance testing is usually carried out during the development of the software and just before launch. In scalability testing, you check how the website or application will program is another software is added to the server or find ways to improve loading time. The test’s primary aim is to find out at what peak the software will prevent more scaling.

Common Issues Observed during Performance Testing:

Performance tests are conducted to make sure the system is free of the fault so that it is ready to be launched in the market. Let’s take a look at some of the common issues that you might encounter during performance testing.

1. Poor Scalability

The system isn’t able to handle the desired number of load that delays loading time leading to unexpected benefits that can affect memory, CPU usage, disk usage, network configuration, and operating system.

2. Bottlenecking

This issue occurs when data flow is halted or interrupted because the website or application isn’t capable enough to handle the load.

3. Insufficient Hardware Resource

This means that there is a lack of hardware that results in memory shortage and CPUs don’t perform well.

4. Software Configuration Problem

It is a minor issue which occurs when configuration settings are set lower than the system can handle. All you have to do is adjust software configuration settings, and it’ll work perfectly fine.

Here are Some of the Best Software Performance Testing Practices:

  1. Run performance tests as early as possible in the development process, so that you can conduct small trials that are successful rather than one big that will have many problems.
  2. You should remember that performance testing is not only for the entire system but can also be used to test individual sections.
  3. You must conduct multiple tests on one part to ensure that test results are consistent.
  4. Make sure you always involve IT developers and testers in the process so that it is an all-around process and you don’t need to keep going between two departments.
  5. Before the test, make sure that you require internal/external or a combination of both is required.
  6.  Devise a high-level plan before the test
  7. Develop script for proof-of-concept for application under test
  8. Configure router configuration, database test sets, quiet network, test environment, etc.
  9. Before the actual test run a dry test to check the script is correct or not

Software performance testing process

  1. Test environment identification-  Identify the physical test environment, tools required and the goals that need to be achieved.
  2. Identify performance acceptance criteria – Charestrisics such as response time, throughput, and resource-use goals and constraints
  3. Plan and design tests- Prepare test environment, select the desired tools, devise strategy, etc.
  4. Configure the test environment – Prepare the required resources to execute the tests
  5. Implement test design – Develop test design in accordance with test design
  6. Execute the test – Run, monitor, validate and collect the test and test data
  7. Analyze test results, make reports, and retest – Consolidate the test data and analyze it. If tuning is required do that and go for a re-test.

Software Performance testing is a key process that can determine the success of your software. If you wish to know how your app can perform in the real world talk to us! 

What is Volume Testing? Why is it essential in Software Testing? (Tutorial)

Volume testing allows one to put the system under the stress of thousands and millions of data files and check them further to working in a perfect working position.

It increases the data load drastically and checks for the efficient work points or the areas that require utmost attention or improvement.
Volume testing le the developer aims to have a tough, efficient, and cost elective software which makes volume testing in the field of software development and maintenance so important.
Typical performance test or the load testing cycle usually is the combination of both volume testing and the performance tuning that ensure in turn that the system is working the international benchmark system of the working.
 volume testing example

What is Volume Testing?

Volume testing is a type of testing which is software based where the software is subject to the stress of huge volume of data, this type of testing is also known as flood testing.
This is basically done to do an analysis of the system performance by increasing data in the given database volume.
This is used for the study of response time impact and the system behavior that can be studied when it is exposed to a high volume of data.
Let us take an example of testing the music site behavior it gives access to millions of users to download songs from the library of thousands of available songs.

What are the benefits of Volume Testing?
  1. Through the help of volume testing, we can identify the load issue, which ultimately can save a lot of money which will be spent on application maintenance.
  2. It helps to have quicker decisions with the better scalability plans and executions
  3. It helps in identifying the challenges and acquires the bottleneck present in different areas.
  4. By doing volume testing you have the assurance that your system is working fully in its competency and capability in the real-time world usage.
What does Volume Testing include?
  1. Test whether there is any data which is lost during the procedure
  2. Check out for the system response time
  3. See if data is stored in the current location.
  4. Countercheck if the data is overwritten without any warning or notification
  5. Now, look at whether the high volumes of the data affect the speed of the processing system or the application.
  6. See if the system application have the desired memory resource r not
  7. Perform the volume test on the whole system.
  8. Check for any of the data volume greater than the specified given requirement
  9. Check for the requirement in the agreement.
  10. See that no larger volume data should appear more than specified.
Procedural steps of Volume Testing

Testing software volume offers the in-depth testing of the performance let us see what are the procedural steps involved in the volume testing.
 what is volume testing

  1. Test management that may include checking for the test environment
  2. Volumetric analysis
  3. Test tool comparison and procurement
  4. Implementation of the system
  5. Building test labs
  6. Building automated test systems and framework
  7. Script development of the system
  8. Test scenario development
  9. Test implementation development
  10. Execution of the test
  11. At the end, producing the test outcomes.
Why should Volume Testing require to be conducted?

Flood testing or volume testing as described is aimed to validate and counter check some of the parameters as well as provide the personified benefits for the software usage.

Let us see some of the benefits of conducting the flood test.

  1. The volume of the software

As the name suggests volume testing is focused on the testing and identifying the basic capacity of the system or the given application in use.
It also provides the required information on whether the given software or the program is normal or of very high volume.

  1. For testing and analyzing the volume of the data

Storage requirement and capabilities of the system or a given application needs to be tested hence volume testing comes in the picture.
It works n the basis of identifying the tuning issues that are present in the software to prevent a system from reaching requires service level agreement.
This is known as volume targets. So we can say that volume testing provide the right in-depth tuning solution and the services.

  1. Detect and minimize the errors

Volume testing minimizes the risk which is associated along with the degradation of the performance, also the possibilities of the breakdowns or failures of under loads which are secondary due to increased pressure n the database.
It looks after the system operations and performance and discovers the bottleneck issues and provides the solutions and recommendations to resolve the outcome in the form of error.

  1. Get the desired information also the deliverables

Along with the given information about the changes in the system application and its performance is the valuable parameter in the IT industry to check for the efficacy under stress of high data volume.
This also helps in the improvement of the structural component and the infrastructural architect which can be provided through the result of volume testing.
This provides detailed explained information for the best possible results.

  1. System response time when verifies

System response time is the important parameter to keep a check upon in the software development and working of its applications.
System response time is known as the time lag between the time taken for the system to display the results and the system receiving the data.
For the successful outcome, this has to be on the minimum side o the scale.
For this volume testing provide best and efficient service in ni time. This is also useful in conditions in which the data input are usually very large.

  1. Check for the loss of the data

Along with the above-described points, another important purpose of volume testing is to ensure that all the given data infused for the purpose of the test to be considered is not lost.
This also allows a correct finding of system efficiency without causing any of the harm to the data.

  1. Storage of the data

Volume testing also ensures that the given data is stored in the correct location in the appropriate manner.
This point becomes important because if the data will be stored properly then only the stored data can provide reliable and accurate data result.

Key features of the Volume Testing
  1. Data that is used in increments

During the process of the inception of software development, the data is usually small and compact in respective sizes in comparison to their successive stage of the development of particular software application on the system.
As soon as the development of the software or its application go on the floor along with this the volume of the data is also increased, this is also done to ensure that the mature application among all can handle the influx of huge amount of data

  1. Auto-generation of the data

As in the software the data requirement is generally in huge amount which is sometimes self-generated or by manual.
When the data is auto-generated this allows the prevention of excessive expenditure which in turn makes the software development more cost-efficient.

  1. No logo can interference of the data is required

As we all know that the main aim of the testing is to check for the performance irregularities and even illogical data among all can provide inputs and the best part of it is that it will not interfere with the testing and can be used for increasing the volume also.

  1. Software performance

As the influx increases, the quality of the software decreases with time.
This makes the application to decline in its function and deteriorates in functionality.
This can be prevented by performing volume testing on time.
Volume testing belongs to non-functional tests related to volume stress and the load that is usually performed to analyze the performance of the system by in turn increasing the data volume.
This volume can be anything ranging from the size of the data at various locations or it could be just a simple file that is needed to be tested.
If someone wishes to test the application or the system with a given specific limit size of the database then testing also requires having that type of setting to check for the performance.

Know More: Adhoc Testing: A Brief Note with Examples

Moreover, volume testing is also used to test the behavior at the site when there are more than thousands of objects which are available under one category.

What are the objectives of volume testing?

There two basic objective of the volume testing which is explained as below-

  1. To check for the load of the volume on the given data representation on the which the whole stability of the system is based and if not cumulated properly than the quality can be compromised.
  2. To identify issues which can prevent the system failure before it reaches above the desired volume targets given in the service level agreement.

Keeping these objectives in mind let the developer or tester have a system that can meet the required expectation.

Characteristics of volume testing

Let us see some of the basic important characteristics of the volume testing

  1. Small quality of data is usually taken during the testing stage of software development.
  2. As far as the volume of the data is concerned if it increases then the performance is nosedive.
  3. The crude base of the generation of test data is the design document,
  4. As the insight of the data is not much required hence the importance of data is not so much driven.
  5. When we are through in the software testing the tester will log and track the results further, this finishes off the final step toward the completing of the test.
Let us see some of the examples of the volume testing

To really understand the example of volume testing let us look at some of its examples-

  • When a developer is working on the application or the system development that has to be used in more than thousands of the laptop or computers then one should stimulate the functions that seem to have the same number of the computers that will be in the use in real time.

We have to understand all the activities to be performed are in real time and should be ultimately focused on the activities which are performance-based.
This may including all things like file opening, creation of the file, and finally, the processing of the data.
If a developer wants to test the application with the database of a given determined size then the corresponding database should be increased in volume by adding more data in the database until the targets are reached.

What are the best practices to perform volume testing?
  1. All servers should be stopped and all logs should be checked.
  2. Properly execute the scenario of the applications manually before loading the test.
  3. Developer should stay out the number of users if a useful result is desired
  4. Balance of think time is must if there is essence contained.
  5. Once the baseline has been established the scope of improvement should be a check upon.
  6. One must be cautious about the new build.

Volume testing and Load testing

  1. Volume testing does the testing of applications on the basis of a large number of files in the database as much as possible whereas in load testing the applications are subjected to a particular level of load to further analyze the behavior pattern of the application.
  2. Volume testing tries verifying if the system response to an expected volume, which may include the time for the increment in the size of the given file. On the other hand, load testing is for checking the performance system whenever a user load is increased, this may further involve the increment in the number of the file.

What are the challenges that are faced by the developers during volume testing

  1. Difficulty in generating memory fragmentation
  2. A key generation is dynamic in nature.
  3. Generated data’s rational integration

Know More: Database Testing: A Quick Guide

How To Do Performance Testing For Web Application Using Jmeter?

Performance testing is done to ensure whether the application is capable enough to bear the load. It can analyse the system’s performance under high load. Jmeter performance testing offers various benefits like it can be used to test the performance of both static and dynamic resources.

Dynamic resources can be JSP, Servlets and AJAX. Static resources can be Javascript and HTML.
There are two kinds of web application testing done using Jmeter.
1. Load Application Testing: The process is mainly used to predict the expected usage by simulating various conditions.
2. Stress Application Testing: Be it any web application the architecture of it can only support a certain number of users at a time. With the help of stress testing load above this capacity will be given on the server after which it behaves weirdly. By doing so, maximum load the web server can handle can be found out.
This can be understood in a much better way by below diagram:
How to create a Performance test in Jmeter
Let’s test the Google website for 1000 users with the help of Jmeter.

  • Add Thread Group

First, start the JMeter application and click on test plan option on the dashboard.          Click on add option and then Thread(Users). Afterwards, click on Thread Group.
The Flow would be:

Add -> Threads (Users) -> Thread Group

  • Enter thread properties in the thread group control panel. You have to enter a certain number of things like :

Number of Threads: Number of users which you want to target to the target website. For example, here we will use 100
Loop Count: 10 (Number of times to execute testing)

Know More: Step by Step Implementation of App Performance Test

Ramp-Up Period: 100 (It is the delay which Jmeter has to wait before starting the next user). 100 seconds is the time which we have used.
Now, you must be confused between thread count and loop count. It is very easy to understand.
Thread count means how many concurrent users Jmeter will create to connect to the web server.
Loop count would be the number of times, Jmeter would simulate one user connecting to the target server.
Suppose in the above example: Jmeter would create 100 concurrent users connecting to the server while one user would be connecting to the server 10 number of times.

  • Adding JMeter elements

There are various JMeter elements which can be used to the test case. Let’s see what they are:
1. HTTP request default
Now, you have created a thread group and you can attach HTTP request element        to it by following the below path:

Add -> Config Element -> HTTP Request Defaults.

In the HTTP request control panel, enter the website name which you have to define. In our example, it would be “”.
2. HTTP request
You can add this element to the thread group by following below path:
Add -> Sampler -> HTTP Request.
Now, in the control panel of the HTTP request, you have to enter the URL      request you want to send to Google. If you give the command as “calendar” in path field, Jmeter will send request to google server. If you will keep it blank then send request to google server.

  • Adding Graph Result to the test output

Jmeter can show the results in graph format. You have to right click on the test plan and then follow the below path:

Add -> Listener -> Graph Results

In this way, you will be able to see the results in graph format.

  • How to run the test and get the test result

You can see the test button on the toolbar to start the testing process. You would be able to see the test result in real time. When you will simulate 100 users which will access Google server then you will get the real-time output.
But all output lines would not be in the same colour. Some would be in black, blue, red and green colours. Black colour means the total number of current samples sent. Blue colour represents the current average of all samples sent. Red colour represents the current standard deviation. Green colour represents throughout rate that represents the number of request per minute the server handled.
How to analyse the graph results in Jmeter
There are two main parameters which you should focus while looking at the result graphs. Throughput and deviation are those which are very important while looking at any JMeter output graph.

Know More: Performance Testing-Types, Stages and Advantages

Throughput is the ability of the application to handle a heavy load. Throughput should be very high ideally. Deviation indicated deviation from average. It should be very low.
In the above graph, throughput is 867/minutes. It means this server can handle 867 requests per minute. This data is of yahoo website. While if you will test then you see throughput is 1000/ minute. Google has higher throughput than yahoo.
These parameters can vary on other factors also. Which include internet speed at JMeter site, current server load at google server, your CPU power and many others. It’s not necessary that you will get the same results every time as they can vary because of other factors.
So start the web application testing using Jmeter and see how much load one website can handle. In this way, you can see why your site stops responding and one of the reasons can be low load-bearing capacity.

If you had some difficulty while doing the above test then try to not connect to the internet via a proxy. If you are connecting through a proxy then don’t connect via that. Try opening a new JMeter instance and then try to run the test.
By following these you would be able to run the test cases with Jmeter. So, keep doing performance testing with JMeter and make your site less prone to vulnerable attacks. All the best!!

21 Best Performance Testing Tools

Performance Testing Tools are boon when it comes to the automation of performance testing.  Performance testing will make sure that your software will eventually become.

  • Scalable
  • Stable
  • High-speed loading
  • Improved server response time
  • High in UX (User Experience)

However, there is a multitude of performance testing tools available at the moment. To ease the confusion we have compiled a list of top 20 performance testing tools that are put to use by testers and software testing companies at the moment.
Performance testing flow chart
What is performance testing?
Types of performance testing
Performance testing a life-saving process for both mobile-based apps as well as web apps to determine how they will perform in certain adverse conditions, I,e you can detect bottleneck of any system easily and rectify it.  in short, response time, speed, load issues, scalability, etc. can be found out
Difference between Performance Testing and Load Testing

                     Performance Testing                   Load Testing
Used to find out the performance of the system, Performance in here means reliability, scalability, etc. Load testing is meant to analyze system behavior at an unusual load
The normal load will also be used Relies on high load
Kind of validation technique Can serve as an evaluation technique
Fatal issues that can affect the software can be detected After tweaking, will the software hold? Can be found out


  1. WebLOAD

WebLOAD is a load and performance testing tool specifically designed for web applications.

  • Rated enterprise-grade, the tool is every enterprise’s first choice to complex testing requirements.
  • Flexibility and ease of use are among the two important strengths of the tool.
  • Furthermore, WebLOAD also supports over a hundred technologies from web protocols to enterprise applications.
  • Helps in correlation, response validation, native Java Scripting, parameterization, messaging, and debugging.
  • More than 80 configurable report templates that will help you in root cause analysis
  • It can be used to integrate with other APM tools and open-source software.
  1. StressStimulus

StresStimulus is a strong performance testing tool because it addresses application scenarios that are difficult to test with other tools.


  • StressStimulus records user actions and replays them in order to emulate variable usage patterns. Additionally, it also monitors load impacts and fixes playback errors.
  • Easy to access UI
  • Supports all app platforms
  • Can integrate with web debugging tool Fiddler
  • Complete performance analytics with graphical interpretations, test reports, etc.
  • Load testing can be automated and recorded
  • Recorded test values can be altered using external data
  • Scripting is not required but the option is there
  • Response time, minimum, maximum, network bandwidth, error rate, requests per second, and average values can be graphed along with VU count.
  1. Apache JMeter

Performance Testing Tools
A Java platform application, Apache JMeter can be integrated with the test plan.Though the tool was initially designed for testing just web applications, its scope has been widened recently. Nevertheless, it works only under UNIX and Window OS.

  • Can be used for performance testing of different applications and protocols
  • Exceptional IDE that helps in test plan recording
  • CLI (command-line mode) that will help in loading test from any JAVA compatible OS
  • Data can be extracted through formats like HTML, JSON XML etc.
  • Dynamic HTML report
  • Completely portable
  • Multi-thread feature that allows concurrent sampling
  • Offline analysis of test results
  1. LoadUI Pro

LoadUI Pro made it to this list because it is the best tool that could create scriptless and sophisticated load tests in the shortest time.

  • Detailed reports can be accessed, and load tests automated on Bamboo, Jenkins, TFS, or any other automation frameworks.
  • Moreover, functional tests from SoapUI can be quickly converted into load tests using LoadUI Pro.
  • Can  be used to perform API load testing
  • Provides insight to improve performance
  • The monitors server response to various requests
  • Existing functional test cases be re-used
  • Using remote agents load generators can be created
  • Various types of loads can be simulated
  1. Load View

Performance Testing Tools
Load View is a cloud-based performance testing tools that make use of real browsers to run a performance test on websites as well as web applications.

  • The test results are made available as real-time online graphs. Furthermore, tasks for simple calls to download content as well as a complex interaction that stimulates user interaction can be performed using Load View.
  • 100% cloud platform. Used GCP and AWS
  • Features of the tool make it a perfect fit for DevOps
  • Number of load injector servers can be identified
  • Load servers located at various geographical zones
  1. Rational Performance Tester

The Rational performance tester is the right option for building an efficient error-free cloud computing service.
The tool can be used for both server-based applications and web applications. Developed by IBM, the automated testing tool comes in many versions.

  • As simple as it can get
  • Can be used to create advanced test scenarios
  • Simple test data and sharing
  • The analysis is extensive and easy
  1. NeoLoad

Performance Testing Tools
An innovative performance testing tool, NeoLoad automates test design, maintenance, and analysis for DevOps, as well as agile teams. In order to support performance testing across the life cycle – the tool integrates with continuous delivery pipelines.

  • Dedicated support for all the latest web technologies
  • Supports script less design and visual programming
  • Detects application-specific parameters automatically
  • Transaction list that has been pre-filled for easy recording.
  • Proxy mode and DNS tunnel mode
  • Supports many web security certificates
  • Special features that can be used to  test audio and video
  1. WAPT

WAPT, the abbreviated form of Web Application Performance Tool is a tool designed specifically for websites and internet applications.

  • Other than measuring the performance of web interfaces, it also enables the user to run performance tests under different load conditions and environments.
  • A simple test design approach
  • Easy to understand HTTP requests that can be altered
  • Emulation of such requests is done by spawning multiple sessions
  • Graphical representation of test analysis
  1. HP Performance Tester

performance testing tools
This tool is a performance testing version of Loadrunner. It lowers the cost of distributed load testing and reduces the risks of deploying systems that don’t meet performance requirements. With effective tool utilization tracking, HP Performance Tester predicts the system capacity to lower the hardware and software costs.

  • Can be integrated into development tools
  • Performance bottleneck can be traced out
  • Has in-built Cucumber 4 BDD template
  • Root cause analysis
  1. Load Impact

performance testing tools
This performance testing tool is mainly used in cloud-based services as it aids in website optimization and improving the performance of web applications. It also brings in traffic to the website by stimulating users to determine the amount of stress and load the website can work efficiently at. Furthermore, the system works well on both Windows OS and LINUX.

  • Powerful scripting environment that can help you in creating API test scenarios
  • Test Scenarios can be created based on virtual users
  • Can be integrated into CI-CD pipeline
  1. Silk Performer

Rated enterprise-class, Silk Performer is capable of testing multiple applications in different environments that hold thousands of simultaneous users.
Moreover, the tool also supports a wide array of protocols. Lastly, Controllers or Individual protocols require no License, and it is customer friendly to use.

  • Existing bump tests can be used to accelerate the test cycle
  • A peak load scenario can be created
  • End-to-end diagnostics to detect error from the user perspective
  • Real-world tests and user pattern can be simulated

performance testing tools
We had talked about JMeter earlier, and is an alternative to it. This tool enables users to perform test scenario creation with scripts and excels in test reporting. GUI tests can be run with real-time results.


  • Embedded browser to create test scenarios within minutes
  • 100% Jmeter compatibility
  • Advanced reporting
  • Can be added easily to CI pipeline
  • Can be used to create virtual users from various geographical locations
  1. LoadComplete

performance testing tools
An easy to use and affordable performance testing tool, LoadComplete creates and executes realistic tests for both web apps and websites. The system requires a 64-bit operating system to work like Windows XP Professional or Windows 7. Furthermore, it also provides detailed reports and metrics which help gain in-depth insights.

  • 60% reduction in the test creation time
  • The load can be created using 1000s of real browsers
  • Real-time VU inspector  and debugger
  • Zephyr and Jira integration for test management
  • Data drive load tests
  1. AppLoader

AppLoader is specifically designed for business applications as it would allow you to test applications by replicating the same user experience from all access points.

  • When a user uses the application, the scripts are generated automatically which can be further edited without coding.
  • Regular updates and strong support is an additional advantage of the AppLoader.
  • An unexpected event can be avoided by Apploaders intelligent engine
  • Triggers alarm if the playback exceeds a certain time
  1. Testing Anywhere

performance testing tools
Testing Anywhere is an automatic tool that works well in the case of websites, web applications, and other objects. The tool is mainly used by developers to find bottlenecks in web applications. Considered powerful, it takes just 5 steps to create a test. The tool is compatible with all versions of Windows OS.

  • One of the best tool when it comes to performance test automation
  • Advanced web recorder
  • Image recognition
  1. Loadster

This desktop-based advanced HTTP testing tool records scripts that are easy to use.

  • In order to validate the response, the scripts can be modified using the GUI.
  • After the execution of the tests, reports are generated for analysis. Loadster system requires a Windows 7/Vista/XP to work on.
  • Dynamic datasets can be bind to the scripts
  • Validators and captures will make sure that the response is coming back to you
  1. QEngine

Also known as ManageEngine, it is a widely used automated testing tool.
These Performance Testing Tools perform remote tests on web services from any geographical location.
Alongside, it also offers other testing options such as functional testing, stress testing, load testing, etc.

  1. CloudTest

CloudTest test websites, APIs, mobile apps and more. The cloud platform could be literally used as a virtual testing lab where developers can carry out tests in a cost-effective way. Though the services are not free and the price differs according to the number of load injectors required, the trial version with a power of 100 concurrent users is still available for free.

  • Used for stress testing websites and apps
  • Rapid test creation without coding
  • Gives you insights on what needs to be done to improve the performance of your website or app
  • Ability to identify and isolate performance bottlenecks
  1. OpenSTA

OpenSTA is the abbreviated form of Open System Testing Architecture. It is a GUI based tool and is believed to be comparatively complex than the other tools present in this list.

  • The results and statistics are taken through a number of tests to carry out the test successfully. Nonetheless, the tool is completely free to use.
  • Record and replay option
  • Results and statistics can be collected during the test run
  • Data logged can be monitored live in between the test
  1. Appvance

Being the first unified test automation platform, this tool erases the redundancies by unifying tests.
21.  Load Ninja
Real user-end performance can be simulated across thousands of browsers with ease. Thanks to Load Ninja
Other features of Load Ninja includes,

  • Record and instant replay options
  • Various metrics to analyze the performance of the software
  • Load tests can be automated and integrated into CI/CD pipeline
  • Apart from load testing, the tool can be used for soak testing as well

Read Also: Top 10 Automation Testing Tools 2019


  • Offers complete integration with Rally, Jenkins, Hudson, Jira, and Bamboo.
  • Reduces cost and allows the team to work together and collaborate.
  • AI-driven
  • Integrates well with CI/CD pipeline

Step-By-Step Implementation of App Performance Test

Mobile Technology is changing the way individuals utilize their smartphones. In spite of the fact that demand is most elevated for consumer applications, enterprise applications are developing as well, enabling organizations to work all the more productively. Testing apps indicate to guarantee that it is running appropriately, it meets its every particular necessity and gives fabulous user experiences.

This may sound troublesome – particularly when there are bazillion diverse gadget configurations where the app must run adequately.

When you consider that noteworthy bit of Google Play and App Store incomes are produced by apps, there is an imperative need to perform mobile app test on as many mobile apps could be expected.

Mobile App Performance Testing Strategies

  • Very much characterized strategy for the end to end performance testing of mobile apps.
  • On device execution (content rendering), server performance (content delivery), and, network reliance.
  • Advanced mobile performance test lab to simulate real-world network conditions.
  • On-demand cloud-based mobile application security testing platform to deliver comprehensive mobile security testing.

Process of Mobile Performance Testing

1. Device Performance

What amount of time does the application take to start? It is the principal performance parameter decreed by the client. After the user clicks on the application the main screen ought to appear in 1-2 seconds as a standard. It should be checked whether an applicationrunning in the background persists in the similar form from it was previously recovered. When this situation isn’t managed appropriately, the data can get lost.

Also, it is obligatory to check applications on various devices. It may come out that application is working smoothly on one device however not on other. Like its working on for Android devices on iOS devices.

Additionally, there ought to be no interference while running it with other apps which could be checked by switching other apps with the testing app.

Thus, these elements must be controlled before releasing the application to the market or providing to the customer.

2. Client Application Performance

This framework part has two factors; native versus browser application, combined with the device’s own particular software and hardware setup.

For the device’s setup, we acknowledge the ordinary variations of model, memory, and processor and its acceptance of those resources when performing standard user situations. The application must be tested with various specifications or RAM and processor such as 1 GB or 2 GB.

By implementing certain functionalities in the application, the memory utilization additionally increments. So, when Testing an application, the memory utilization by an application ought to be checked.

Let’s See a Video Representation about How to Test Performance of Your Mobile App in 20 Minutes

For mobile, we consider a local app still as a client in the event that it requires remote access to a server application. The native app is now and then utilized for a better security, presentation, and more adaptable setup instead of a browser-based application.

Mobile browser-based app performance is normally reliant on the performance of server and network application. The performance is frequently slower accordingly and prompts a lessened user experience. Also, a few browsers may have higher execution than others as there’s no rule.

For a native mobile app, the client’s view of execution can be updated relying upon the amount of the app and its data remains on the server application versus the local device.

3. Server/API Performance

Your server application additionally should have the capacity to perceive the browser/device combination so as to render accurately.

Checking the server performance is like estimating site or web application performance where we have to break down our analysis into the parts of the server that are giving the administrations incorporating the application server, database, and related hardware.

The application should control the data productively that is sent from the server. It must not require excessive time while loading information. In certain applications, data is sent in a predefined format. So, before showing it in the application, it ought to be changed to a significant format. In this process, applications sometimes turn out to be slower and response time turns out to be longer.

Also Read : Mobile App Security Testing Checklist Every Developer Must Have

Likewise, the number of calls the testing app to the server created from the application ought to be less.

In case, the server is down or inaccessible we can save information in the local database. In this way, at whenever the server is down, we can demonstrate data stored in the local database. The backup/failover server must be in persistent replication and synchronization with the principal server.

4. Network Performance

The app may perform uniquely on different networks as network protocols affect delays and throughput. The application must be tested on all different networks with variable speed. The application ought to be checked on 2.5G, 3G, and 4G networks. Both mobile and Wi-Fi networks are incorporated into this.

Additionally, the operation of the application must be checked when both the networks are accessible and switching happened from one network to the next. Latency is reliant on the app in how effective it is in its transmission technique algorithms, and the quantity of information transmitted too (frequently called payload).


If there is a delay in accepting data on the network, at such point, it’s named as jitters. It is an issue with the packet switch networks or connectionless networks. As the data is dispersed into packets, they can go by a divergent way from the sender to the recipient. As the information reaches the expected location, it ends up mixed than it was initially sent. On account of Jitters, the mobile application ought to be sufficiently capable to control it.

You have to Show the suitable warnings to the end user, either to wait till the system responds again or resend the demand.


Due to consistently developing demand for mobile applications, leaders are concentrating on making mobile app performance testing strategies before implementing the app for their clients. It is essential to building an application with all functionalities and features required by the client and which is valuable to the application user. However, it is considerably more basic to have a thorough mobile performance testing plan before the application is launched.

20 Open Source Mobile Application Performance Testing Tools

Do you have to deal with your extremely slow application/server every day? Has your latest feature undergone a degradation or memory leak? The only way to verify whether your application is performing well or not is to do a regular check.

app testing

However, how do you know which tool to choose and which not to? Through this post, we will take a look at the leading open-source sources for load and performance testing.

  • Sauce Labs

Sauce Labs is pretty popular among these days and runs over a million cloud-based tests every day. This automated mobile app testing covers over 800 different browsers to ensure bug-free user environment. Furthermore, the testing cloud runs tests in parallel and isn’t time-consuming at all. It can accommodate even the largest testing volume within the shortest possible time.

  • TestComplete

With TestComplete, it is now possible to run repeated UI tests across native and hybrid mobile apps. TestComplete is compatible with both Android and iOS devices, and it is possible to create automated test scripts or choose from programming languages including Python, VBScript, and JavaScript.

  • Calabash

Calabash is used to perform automated functional testing for native mobile apps. It comes with two open-source libraries for both Android and iOS devices. It can also provide APIs for touch screening experiences and works well with Ruby, NET, Java, and many other programming languages.

  • WebLoad

WebLoad is currently available in around 50 virtual users and is 100% free to use. It enables you to do a stress test to let you know of the device’s performance. The tool also comes with an application that helps in recording scripts directly from a mobile device

  • Kobiton

Kobiton provides access to devices for running manual and automated test. This mobile device cloud platform is built on top of the Appium open-source framework and could be used to test across devices without script modifications. The main feature of the tool includes commands, screenshots, faster identification, and automatically generated activity logs.

  • SeeTest Continuous Testing Platform

The SeeTest Continuous Testing Platform enables continuous testing of mobile applications to boost release cycles and increase quality. The tool continuously tests all types of mobile apps under real end-user conditions. To provide rapid feedback, and to speed up the release cycles, the tests are run in parallel on numerous devices.

  • Appium Studio

This free toll benefits the user in a multitude of ways. The main benefits include the ease of writing and recording tests using device reflection, Object Spy, and unique XPath. The tool even features running tests outside your application including audio features, barcode scanning, TouchID, and more.

  • MonkeyTalk

MonkeyTalk is an open-source tool that is built out of three components – IDE, Scripts, and Agents. Everything from simple “Smoke Tests” to tough data-driven tests could be done using MonkeyTalk which works well on both Android and iOS devices.

  • UI Automator

This open-source run tests only across Android devices. The tests are run using automated functional test cases, and UI Automator framework is built using the scripts written in JavaScript.

  • iOS Driver

As the name suggests, the tool is compatible only with iOS devices. Previously, the tool used to run rather efficiently on emulators than devices. But the recent versions run on devices as well as a much slower rate than on emulators. There is no requirement to change the app code or load any additional app for testing your mobile device performance, as the tool comes with in-built applications.

automation testing service testbytes banner

  • Robotium

Robotium is yet another tool that works only on Android devices. The test automation framework does its job well on both native and hybrid apps. Alongside, the tool also allows the user to write function, test scenarios, and systems.

  • Selendroid

Explicitly designed for Selenium and Android UI testing, the open-source framework of this application interacts with emulators and multiple devices simultaneously. The test ought to be written via Selenium 2 client API, and the test code is based on Selenium 2 and WebDriver API.

  • KeepItFunctional

KeepItFunctional keeps your iOS device functional by running test to make sure that your device performs its best. The open-source framework allows amble automation testing of iOS apps.

  • Egg Plant

Developed by Test Plant, eggplant is a commercial GUI automation testing product used for both Android and iOS app testing. The tool is useful for image-based testing, network testing, mobile testing, and cross-browser testing.

  • Ranorex

Ranorex is used to test both web-based and mobile applications. Ranorex supports a wide array of tests including acceptance test, data-driven test, cross-device tests, automation tests, web tests and more. Nonetheless, Ranorex is mainly used to run functional tests on native iOS apps, and mobile apps.

  • Silk Mobile

This automated functional testing tool is the brainchild of Borland. The tool supports testing almost all operating systems including Android, iOS, Blackberry, Windows Mobile, Symbian, and HTML 5. Silk Mobile also features a visual scripting and advanced scripting mode which can be altered based on the organisation’s requirements.

  • SOASTA TouchTest

Launched by SOASTA, this functional testing tool aids in continuous testing for both native and hybrid apps. The tool helps in boosting your device’s performance after speeding up the mobile testing on both open-source and commercial platforms.

  • Testdroid

Testdroid includes a set of mobile software development and testing products that are developed by Bitbar Technologies Limited. The tool helps in amble testing of mobile apps with automation and manual testing.

  • TestFairy

This Beta Testing platform for mobile apps helps to perform testing with an additional feature of video recording in case of both Android and iOS apps. TestFairy is a free mobile testing tool that comes with open-source plugins and API.

  • Frank

Frank is presently the only test framework that features integration of Cucumber and JSON. The tool helps the user to write structures acceptance tests and requirements. The tool makes it easy for the user to work with the tool without having to make any modification to the app code.

testbytes game testing banner

With so many choices, choosing the right mobile testing app for your device can be a hectic task. With the above list, you would be able to find the one tool that suits your need.

Methods For Testing Mobile App Performance Using LoadRunner

People using smart phones require the mobile apps to perform with the same effectiveness as the desktop software does. Due to inundation of numerous applications in the virtual store, the competition is extremely high. As a result, robust apps are in demand that pass rigorous testing parameters. If you are an app developer, use LoadRunner for mobile applications as it works extremely well with the native version. Although web apps are tested with the help of open source platforms, it is the LoadRunner that plays an important role to enhance the capability of the mobile based software.
app testing
Testing is a complex process where numerous devices right from Android to iOS are involved. There are different versions for native and web applications, however LoadRunner can resolve all the issues with the help of certain protocols.
It records the browser and native scripts that query the server with the help of http/html protocols. The whole process takes place at the transport layer of the TCP/IP model. Network traffic is recorded in a separate file called PCAP and then it is used to create a visual script. Even third party emulators can be used to generate the script logic.
True client essential for native mobile:
True client technology is used to record the scripts of the browser based or hybrid mobile applications. Apps are loaded onto the mobile devices and are tested end to end mode in order to find out errors. To make the process successful, one should install mobile test center app on the device. It consists of emulators that help to perform, extensive testing and build the most memorable apps in the market.
Mobile web protocol:
The protocol plays an important role in recording the user activity in the mobile applications based on the browser scripts. The whole process takes place in the TruClient browser that is modified to be an emulator.
SMP or SAP mobile platform:

  • The protocol helps the users to create .NET scripts according to their requirements an specification. Files are auto generated on SMP, however the script should not use threading as is the norm in .NET and Java environment because they might degrade the scalability of the testing process.
  • In addition, threads might hamper the measurement procedure at the client’s site. Users cannot invoke functions from the thread because their behavior remains undetermined.
  • In order to record the script using SMP, it is vital to generate the file such as Action.CS, Vuser_ init.cs, Vuser_end.cs.
  • The user should click on the new script and solution link and select SAP mobile platform.
  • Once the files are generated, they are copied into the script folder.
  • After the process is completed, you should invoke the save button, close the script file and reopen the content.
  • Thereafter, the location of the .DLL file needs to be added to the Shared DLL folders situated under the .NET settings located in the Run time settings menu.
  • You can replay the script to watch it in action with the SMP protocol.

Therefore, LoadRunner is useful for converting captured network traffic to HTTP user script, using either the provided tools or by using conventional capturing tools which can help you produce performance scripts for mobile app performance.

5 Tips to Setup a Better Performance Testing Environment

Performance testing is the process during which a product’s quality or its ability to function in the required environment is evaluated. As a non-functional testing technique, performance testing is conducted to evaluate a systems ability in terms of responsiveness and stability under workload. This process is conducted on three major attributes, which includes scalability, reliability and resource usage.
app testing
A number of techniques can be used to check performance of a software or hardware in a performance testing environment setup. This includes:

  • Load testing is the simplest form of testing and is basically conducted to understand the behaviour of the system under a specific load.
  • Stress testing is conducted to check a system ability to cope with the increased load, if any. It is performed to determine the maximum capacity of the existing system.
  • Soak testing, also known as endurance testing, is a type of testing done to verify a system’s ability to perform in situations of continuous load.
  • Spike testing is conducted by abruptly increasing the number of users of a system and determining how the system performs under such load.

There are a number of simple ways in which one can ensure accuracy and better results in the tests. This can be done using a better performance testing environment setup, which can be done in the following ways:
1. Detailed knowledge of AUT Production and Test Environment      
 It is the responsibility of a performance testing engineer to have complete knowledge and awareness about the AUT production environment such as server machines, load balancing as well as a number of other system components. These details, once known, should be properly documented and well-understood before initiating the initial stage of the performance testing
It is also important for an engineer to keep himself/herself aware about the complete details of the AUT architecture and to make sure that the same architecture is being executed in the test environment. This is because, having any sort of difference between the two can lead to the wastage of time, cost of production and effort.
2. Isolating the test environment
 It is important to ensure that there is no activity which is being carried out on the performance test environment when there is someone already using the system. This is because the results of every performance test are different and it might get difficult to implement a new bottleneck every time in a test environment when there are also other users currently active on the system.
Apart from this, heavy load on any application server affects its performance. This, in turn, might not allow the other real time application users to successfully complete their tasks when a performance task is already under execution.
3. Network Isolation
It is important to ensure that a sufficient network bandwidth is available for your test as network bandwidth is essential to achieve accurate performance test results. In case the network bandwidth is low, the user requests begin to produce timeout errors. Therefore, one should make sure to provide maximum network bandwidth to the test environment by isolating the test network from other users.
4. Test Data Generators
Database records have an important role to play in the validation of any tests. Therefore, database reading, writing, deletion and updating are the most performance intrusive actions in any application.
Since there is a high probability of an application’s test failure in the production environment if it is conducted on lesser database records as compared to the test records. Therefore, it becomes the responsibility of the performance engineers to make sure that the number of test records are same in both the test environment system and database. In case, the database is small, it is recommended to pick some tool from the available ones and generate the required test data for better accuracy.
 5. Removing proxy servers from network path
Performance results can be highly affected if there is a proxy server between the client and the web server. If the mid of client and web server has a proxy server, it is certainly true that the client will be served with data in cache and will stop sending any requests to web server. This, in turn, can lead to a lower AUT response time.

A performance engineer can deal with such issue by transferring the web server in a secluded environment. Another way is to strike directly to the web server, which can be done by editing the HOSTS file by including server IP address.
Performance Testing Production Environment
There are a number of advantages and disadvantages of conducting a performance test in production environment. Some of these include the following:

  • There is no need to reproduce the production site data set
  • Validating the performance test results performed on test environment is possible.
  • There is a reduced cost and time involved in test infrastructure.
  • Application recovery process and its complexities are well known.


  • Real application users end up receiving slower application and errors.
  • It gets difficult to identify the bottleneck root cause in the presence of real application users.
  • It is very likely that the access to real users might have to be blocked so as to properly achieve the performance test results.
  • In case of generating lots of data on production database, database may become very slow even after the test.

Once the test performance testing environment setup is ready, one can always compare it with the production environment on the basis of several factors such as the number of servers, load balancing strategy, hardware and software resources, application components, to name a few.
Above all, it is important that the required tests are conducted properly so that there are no faults pending in an application when making its use in real-life situations.

The 3 Types of Software Performance Testing, Their Benefits & Challenges

You might be familiar with performance testing; a general term used to refer to various types of performance based testing on different devices. Software penetration testing is of different types, each of which has specific purposes. Unlike other software related tests, it is a bit complex and has its own advantages and challenges.

app testing

If you are a developer or a person doing software business, you should know about the advantages and project risks connected to different types of performance based testing. We are going to give a clear idea about the different types of testing and terms associated with software performance testing via this article.

Let’s know about Performance Testing

Why you should do performance testing? You should do performance testing to ensure that the parameters such as speed, stability, data transfer rate, efficiency, etc. of your software meet the required standards.

Recommended Read : 5 Top Factors in Website Usability Testing [must-read]

Three Types of Performance Testing

There are three types of software performance testing in general – Performance Test, Load Test, and Stress Test.

  1. Performance Test


  • To make sure the speed, accuracy, and stability of the software.
  • Performance test is vital to authenticate the responsiveness, scalability and reliability features of the software under test.


  • Validating the basic features of the application give you confidence to announce notable business decisions based on your software
  • Testing helps you know whether the features of your software are set in such a way to please the users
  • Able to detect the mismatches and rectify it before the software gets published
  • Performance testing enhances your optimization and capacity planning efforts


  • Some functional errors are only visible under load. There is a chance for not detecting such errors while doing performance testing.
  • Testing ends as a mere process if it is not programmed and executed carefully.
  • If testing is not performed on various devices, it might cause variation in results and hence users experience difficulties.
  1. Load Test


  • To validate the performance of the application on varying load conditions.
  • To ensure the endurance of an application.


  • Validates the throughput needed to tackle the estimated peak load
  • Verifies the efficiency of a hardware platform.
  • Assess the sufficiency of a load balancer.
  • Spot the concurrency related issues
  • Detect functionality errors under load. Identifies functionality errors when there are load variations
  • Collects data for scalability and capacity-planning purposes. Gather information for scalability purposes.
  • Able to estimate whether the application is suitable for multi-tasking.
  • Estimation of load capacity is possible


  • Not programmed to principally concentrate on speed of response
  • Comparison of load test results is limited to similar load-related tests

Read Also : 20 Amazing Application Penetration Testing Tools For Every Tester

  1. Stress Test


  • To find out the performance of an application on high load conditions.
  • The real objective of stress testing is to spot bugs and error on high load condition. This enhances the trust on your product in the market.


  • Verifies whether there is the possibility for corrupting data by overstressing the application
  • Able to predict how long an application can sustain without errors under peak load conditions.
  • You are able to assert the safe load capacity of your application to avoid imminent failures
  • Can avoid security vulnerabilities
  • Able to anticipate common application failures



  • Since stress tests are not all realistic by design, the possibility of approving test results is low.
  • Unable to guess how much stress is worth applying
  • Chances for application or network failures are high if testing conditions is not isolated.