For performance testing departments
Centralized management of test assets and summary display from the project or system dimension are two effective management methods. These test assets include scripts, defect descriptions, test records, test reports, project requirements and other materials. By classifying these materials, new test engineers can quickly understand key information when the original personnel are missing.
Use the system to record performance test plans, requirements, goals, defects, and test result indicator data (similar to functional testing).
For development department
During the performance testing phase, development engineers are mainly involved in performance defect analysis, performance tuning, etc. The defect descriptions produced by the performance testing process are their most important asset.
It mainly displays performance defects and location cause information to developers.
For business departments
Need to convert technical data into business indicator data
❑Scenario: Describe the business scenario covered by the test and the number of nodes in the test system. For example, there are 60 nodes in the standard order process.
❑Business distribution: Displayed according to the traffic proportion of the current business scenario, such as homepage 35%, entering the menu 35%, adding to the shopping cart 20% (including anonymous users), and ordering process (including adding to the shopping cart) 10%. In addition, other data must be matched. For example, when the number of concurrency is 200, TPS is 978.78 transactions/second, orders are 61 orders/second, and the system processing response time is 2.5 seconds.
❑Business conclusion one: If the overall waiting time for user operations is 5 minutes (300 seconds), the number of online users that the system can support is approximately 978.78 ×(2.5+300)=296080. ? ? ? ? ?