Performance Testing, Load Testing, and Stress Testing

What is performance testing? Performance testing is used to evaluate the performance of a particular system in a specific situation. Performance testing includes load testing, Stress testing, capacity testing, volume testing, endurance testing, spike testing, and reliability testing. Performance testing does not give a pass or a fail, it’s done to set a benchmark of server response time latency, and render time. So this type of testing can be used to test speed, and scalability.

Load testing is a type of performance testing. It’s done by increasing the load on the application until it reaches the time threshold. It’s used to identify the limits of the systems database, hardware and network.

Endurance Testing is closely related to load testing and it is used to calculate the time to failure and time between failures.

Stress Testing is done to test the applications behavior past the normal load conditions. An example of stress testing is if you were testing an application that has a 10,000 user limit, and you increased the load to 11,000 to see how the application would respond.

All of these test methods have different functions and can be used in unison to thoroughly test an application.

 

Performance Testing vs Load Testing vs Stress Testing http://www.softwaretestingstuff.com/2011/09/performance-testing-vs-load-testing-vs.html

 

Other articles i looked at:

http://www.softwaretestingstuff.com/2011/09/how-to-prioritize-bugs-numerically.html

http://www.softwaretestingstuff.com/2013/08/types-of-etl-testingwhat-is-covered-in.html

http://www.softwaretestingstuff.com/2013/09/model-based-testing-mbt.html

http://www.softwaretestingstuff.com/2013/01/points-to-take-care-while-doing-testing.html

From the blog CS@Worcester – Site Title by jonathanpaizblog and used with permission of the author. All other rights reserved by the author.

REACT

The most common situation testers find themselves in is producing a bug report. So what’s the process? You REACT accordingly.

R eproduce

The first step to prove that it is truly a bug and not a mistake is to recreate the steps to reproduce the bug. People don’t believe hearsay; they want to witness the problem.

E xplore

Take a second before reporting and look around to see if this bug is part of a larger problem. In the end, fewer reported problems are better.

A nalyze

Determine the severity of the bug and who it will affect the most. Testers are advocates for both users and quality.

C ommunicate

Report the bug, and give an informed representation of the issue and its impact. Most likely this includes sharing information at a meeting, or speaking with developers separately.

T riage

Testers continue to assist in helping others duplicate the issue, clarifying questions and any other knowledge of said issue.

 

http://www.brendanconnolly.net/react-to-bugs/

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Automated Combinatorial Testing for Software (Week3)

Based on NIST website evidence suggests that nearly all software errors are triggered by the interaction of one to six parameters.This article posted by National Institute of Standards and Technology is saying that if faults in  systems can be caused by a combination of n or fewer parameters, then testing all n-way combinations of parameters can provide high confidence that nearly all faults have been discovered. NIST is creating methods and tools to generate tests for n-ways combinations of parameter values. They are using combinatorial testing algorithms for designing arrays and automated model checking. This work will have applications in high assurance software, security and safety. This research project is interesting because NIST is creating new ways of testing. In order to apply combinatorial testing it is required to find set of test inputs that covers all t-way combinations of parameter values and to match up each set of inputs with the expected output, this way of testing is traditional and difficult problems but the cool thing is that these problems can be solved with the new algorithms on currently available hardware. Some of the elements for this project/program are fault localization,  integration into the development process, improved covering array algorithms and distribution of interaction faults. I think Automated Combinatorial Testing is a very interesting process to solve problems especially when we use new algorithms to solve problems.
Citation 
https://www.nist.gov/programs-projects/automated-combinatorial-testing-software-acts

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.