Performance testing is done in order to determine where there are bottlenecks in a given application, establish a baseline so future testing is able to take place, provide support for any performance tuning efforts, determine whether the testing team has complied with testing goals that have been set and compile data to help stakeholders make crucial decisions that relate to the quality of the program overall. Both testers and developers will also be able to make estimations regarding hardware configurations that are necessary to enable the software to run successfully. When software is adequately tested, this will ensure that the program will work well upon release. There are a number of activities that take place during the performance testing process.
Identifying Testing environment
The first thing that all testers absolutely must do is become acquainted with the testing environment. This entails knowing what sort of hardware will be involved, and it also requires that testers will get to know their teammates and project managers. In addition, it is necessary to find out which tools will be used during the testing phase and get familiar with them.
Make Note of Acceptance Criteria
After testers have become familiar with their testing environments, they need to familiarize themselves with the acceptance criteria. Testers must find out which objectives have been set and learn which steps have been outlined in order for these objectives to be met.
Depending on the type of application being tested, specific tests may need to be designed. For instance, tests will differ from web applications and those that are designed for a single person’s use on a computer. A web app will be subjected to all tests, whereas a software program for single use on a computer will undergo isolation testing and configuration testing.
Execute Tests That Have Been Designed
Once tests have been designed, it is time to execute them. In order to ensure the execution process runs smoothly, it is advantageous to come up with some sort of schedule as to when these tests will be executed and when they are scheduled to finish. It is also beneficial to decide who will complete which tests, especially if a large team will be working on the project.
Analyze the Results
Once testing has been completed, the team must collaborate together to analyze results. If a tester is working independently, he or she must do this process alone or work with the project manager or developers. Testing analyses can drafted up in the form of spreadsheets for easy reading and careful record keeping.
Draft a Report
After completing testing analysis, a report is then drafted. This report will provide an overview of the program being tested, discuss which tests have been run and explain the outcomes in immense detail. Upon completing the report, it is sent to the project manager or directly to the software developers.
Retest the Application
Many times, the application will need to be retested after fixes have been applied. This is to see if any problems still persist. If all fixes have been applied successfully, the software is then ready for release.
No matter which kind of application is being tested, it is crucial that all activities are completed. Failure to complete all performance testing activities will result in serious problems down the line that may be quite expensive to fix.
- License: Creative Commons image source
Eric Blair writes about load testing tools, mobile application testing tools and other related services.