Test Process Management
Testing is a process, not only using test tools to record scripts and run the scene, but mainly in the pre-test design and preparation phase, as the software project development needs good system analysis and design, testing at the beginning of the system also need to have a certain understanding of the test, know what and how to measure, Then, based on the analysis and design of the preliminary preparation, the whole process can be divided into four stages: design, preparation, execution and analysis.
Design
Understand the condition of the system under test, including the environment and hardware configuration of the system under test;
Understand the overall considerations of performance testing, including the purpose and scope of testing, planning and scheduling, system-hosted scale, expected results, people and roles, and more.
Design test plans and scenarios.
Get ready
Start preparing test-related work, including test environment and test tool preparation, test case and scenario preparation, test data preparation, script recording, performance monitoring verification, etc.
Perform
Perform the performance testing phase. With recorded scripts, performance tests are performed through scene simulations, and monitoring data is collected at different runtime settings depending on the purpose of the test and the execution phase, which we'll discuss in more detail later.
Performance test run can be divided into several stages, such as benchmark test, configuration test, performance test and stability test.
Analysis
Collect test Performance performance data, monitor data and logs, conduct performance test results analysis, and collate performance test reports. At the end of this phase, after the bottleneck is fixed, the configuration is modified and the problem is resolved, the execution phase is repeated and the performance test is re-tested to determine the final performance situation.
Risk Assessment and control
As with software development, performance testing is also risky, where the risk refers not to the destruction of production data, the system is crushed, and so on, but refers to the performance testing process will meet a variety of problems, resulting in performance testing can not proceed.
Performance testing as a sub-project in software testing, software testing is a sub-project, so the risk assessment and control of performance testing is similar to the risk assessment and control of software development in software engineering, that is, to take into account the various risks that may be encountered in the work in the plan, and to propose ways to avoid risks, In the process of work, at various stages of the summary period, or periodically to review the expected risk, to see if it happened, whether it has gone through the risk point, for the risk has been exposed, it is necessary to timely according to the recommendations to avoid the risk of the test work to make corresponding changes.
What should be prepared before the performance test?