The number one application performance testing objective is analysis of the test results. In fact, performance...
testing is backwards because many software development businesses conduct application performance tests, but fail to analyze the results. The main objective of testing must be to analyze results and determine where the application's performance can be improved.
When scheduling application performance tests, first plan to analyze the results. It's not enough to run test scripts, developers or performance engineers need to think through the results. Plan time to fully analyze test results and gather data that is actively used to design application improvements.
The second application performance testing objective is defining the measurements. What is the definition of 'fast enough?' Performance testing is a tool for improving performance, but, in order to improve, you have to know what the current baseline is. Execute the performance test during each deployment and measure how the application currently performs. Determine if the timing is consistent, or if it doesn't have a pattern. Define the minimum performance values expected. When an application is run continuously for periods of time, it provides a baseline to work from. As the business gets more sophisticated with performance testing, add load, check for stability and determine at what points the application performs the best. Measuring application performance is the only way to know how well the application scales and allows the opportunity to plan for future improvements.
The third application performance testing objective is to create authentic, planned and thoughtfully crafted performance tests. Do more than just using the free add-ons available in many tools. Performance testing is too important to the application's success. Customers leave slow-performing Web or mobile sites. The winning application is the high performing one. Many software development businesses fail to take performance testing seriously. It deserves focused effort, including time to design full performance test development.
Slapping performance testing together or using simple, pre-fab tools is not the answer. Either use a performance engineer with specific domain knowledge, or allow development and quality assurance to design and develop application performance tests that generate data that can be analyzed and used to improve performance. Application performance is serious for the success of the business. Take it seriously and test thoroughly.
Using application performance modeling techniques
Addressing application performance early
Dig Deeper on Automated Software Testing
Related Q&A from Amy Reichert
The software testing profession is changing rapidly, thanks to DevOps and automation. But some of the skills you'll need to keep up are surprisingly ...continue reading
Trying to identify bottlenecks in the software testing process can be challenging, but starting a lean QA effort can help. Expert Amy Reichert ...continue reading
You can't test something if you don't know what it's supposed to do. Often, testers have a very incomplete understanding of what they're testing. ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.