Exp. Share | Performance Testing tutorial, step by step, complete guide (1)
51Testing | Software Testing Service Provider |Tuesday, 10th Nov. 2020
Why we need performance testing process criteria?
A standard performance testing implementation process enforces the testing workflow control, clarifies clearly the task need to do for each stage, guide the tester carry out the testing correctly and orderly, and increase the efficiency of each role in the performance testing. The performance testing implementation process we share this time is the guideline of a standard process, hoping that it can help you to be master of this domain as soon as possible.
Performance testing implementation process
There are five stages for performance testing: requirements research, testing preparation, testing implementation, testing report, and conclusion.
For each stage, what should we do? And what should we pay close attention to?
- Requirements research
The main task of the research stage are as followed: set up a testing team, create a project, analyze requirements, build a model, customize a performance testing plan.
During this stage, you should focus on requirement research, requirement analysis, and model building.
Requirement research is divided into two steps, requirement research, and requirement analysis. This stage is a must-to-do for performance testing. The output document of this stage is <X project performance testing requirements>. And the model building of this stage is mainly the business model.
The performance testing implementer takes the lead of the required research while the product manager, development engineer, and operation engineer coordinate.
Here is the main content of requirement research.
The performance requirement of the system’s online environment, such as performance requirement, reliability requirement, maintainability requirement, etc.
Other information related to system performance includes system information(online environment hardware, parameter configuration, system architecture and deployment, connected system deployment, etc.), business information(core business logic and process, trading list, trading information, and service distribution), production problem, file, etc.
After that, what you need to do is to understand the system and technology by summarizing the collected information.
After collecting and understanding the information, requirement analysis will be the next step.
Firstly, the tester analyzes the information collected from the requirement research and converts the requirement to a specific index value of performance requirements.
And then, the tester converts the performance requirement value under the online environment to the value required under the testing environment according to the difference between the testing environment and the online environment.
The main content and normalization of requirement analysis are as followed:
- Performance testing requirements: the performance testing value and requirement value should be described correctly.
- System scope: the testing scope on which the performance testing requirement value relies should be described correctly. It should include the logical schematic diagram and information about the associated system of the testing scope. When testing a partial link of the system, we should clarify the detailed testing scope and associated sub-systems.
- Environmental difference analysis: the testing environment on which the performance testing value relies should be described correctly. For example, the overall network topology diagram, the equipment(numbers, model, source, operation system), software configuration, important parameter configuration, etc. Meanwhile, the above information on the online environment should be described correctly, and the difference should be carried out.
— — —
51Testing: The second part is coming soon.