it's all about the Performance Testing
We perform load and performance tests to make certain that our hard work designing, programming, building and creating websites and applications do not fail when they go live.
We need to ensure that these apps and sites are ready to be deployed on a production server, that they can handle the varying loads or influx of concurrent users.
Usually, we run our performance test check, then analyze the report. And the performance reports better have lots of pertinent info and they had better be as clear to read and analyze as a blue sky on a sunny morning.
Only after analyzing the report (and tests in action) can the right decisions be made as to whether the app or site is ready to go live.
I.The scenario description with main breakpoints during test runs.
The person who will read the report did not perform the tests and may have little to no knowledge about what was tested. So, be as clear as possible.
II.The total number of testing cycles.
III.Both the inscope and outscope;
Do not add all graphs rendered after testing. The best testing reports should have a few select graphs, generally those that will prove optimal output at the end of the article presented.
If your report contains only raw statistics, it is almost impossible to understand the test results. The performance tester is the point person, obviously, who must provide the interpretation.
VI.Some formulas (if they are applicable to the particular test results); Reports that are full of formulas are very challenging. It’s extremelly difficult for the non-tester to wholly understand what lies behind the many sequences of math symbols.
VII.Comparison with baseline or previous results ;
Is the current situation better or worse? What changed since the last execution? What changes were made in the application code?
VIII.Identification of bottlenecks in the application;
If any issues were found, then an investigation to debug and test again should begin.
IX.Recommendations as to how to resolve the bottleneck;
Add recommendations regarding what should be checked and which parameters should be adjusted.
While it is definitely up to the individual performance tester, we suggest several of the most common:
That’s why it’s not good to include a lot of statistics, because managers may not have the need or understand it.
Most important to include: