1. Performance test report writing skills
After analyzing the results and drawing conclusions, performance test engineers send them to relevant personnel in the form of text reports. This is the performance test report. In addition to the written text, if possible, the company will also convene a special meeting for report explanation and result analysis. Therefore, the performance test report is the work result of the performance test engineer, and it is also an important window for other departments of the company to examine the performance test engineer's ability. Writing an excellent report is very beneficial to the company's decision-making and personal career.
1. What is a good performance test report
Performance test reports in actual work generally exist in the form of Word/PDF documents or emails. The readers of the test report are generally managers of the entire project team or even higher-level colleagues, such as developers, etc. They do not necessarily have much test background knowledge. Therefore, the test report should try to avoid test terms and use easy-to-understand narration of words. In addition, it should not be a simple list of performance test results: because readers are superiors or other colleagues, they don't have much time to care about the specific details of the test, but only care about whether the test conclusion in the report is reasonable and the content of the conclusion. This is a matter of principle that performance test engineers need to pay attention to, that is, they cannot write reports from themselves, but should be considered for the readers of the reports.
According to this principle, to complete a good performance test report, it is best to do the following:
Timing of reporting.
Reports can be discussed with the Test Lead.
Effectively summarize and summarize test data.
Reports should be clear and easy to read, incorporating graphs, but not abusing graphs.
The report should have strong logic.
The report should have a sense of hierarchy, with distinct and clear distinctions between several parts.
The test report is generally divided into several parts: test purpose, test method, test data summary, test result analysis, and conclusion. The requirements in actual work are not the same, and some companies have their own templates, so there are no certain rules on the document structure. But in terms of content, if the above points can be achieved, it is not difficult to write a good performance test report.
2. Detailed records of intermediate conclusions
Detailed recording of intermediate conclusions is very important for analyzing performance test data. In actual work, it often happens that the initial conclusion is inconsistent with the final conclusion. After analyzing each data table or graph, if possible, we must record what problems the graph or table illustrates and what questions there are. In this way, test engineers will gradually have a clear picture of the performance of the entire web application, and it is also conducive to backtracking after making wrong conclusions and finding errors in analysis ideas.
In short, for the analysis of performance test results, there must be a serious and responsible attitude and meticulous and scientific methods. With them, it is not difficult to draw correct conclusions.
3. When to submit the report
Different from functional testing, etc., performance testing is not carried out continuously during the entire web application development process, so performance testing reports are generally only available to limited readers around a few time points (such as before the end of a certain stage). This can easily give the impression that performance testing is not as important as functional testing, and if time is tight, it doesn't even need to be done very systematically. This will affect the sense of accomplishment and motivation of performance test engineers. Therefore, it is necessary for performance test engineers to create an atmosphere in which performance testing continues to exist. Doing so has several benefits:
(1) Cultivate colleagues' attention to performance testing and popularize some knowledge of performance testing. This helps the readers of the test report to better understand the process of performance testing and the content of the test report. Since it is rather abrupt to actively introduce performance testing knowledge in daily work, according to the actual situation, you can choose to select a short time to introduce some concepts of performance testing in the meeting of the testing department.
(2) It is conducive to the cultivation of the spirit of unity and cooperation in the project team. Sharing yourself can achieve more. For example, when the developer has just modified some code, the performance test engineer may wish to do a small test. If the performance is improved compared to the previous one, the result can be sent by e-mail less formally, and at the same time The performance test data can also be placed in the server in the project group and shared with all members. In this way, developers can get good news about performance improvement and encourage each other. The work of performance test engineers can also be seen by the entire project team. Colleagues who like to study can also view data in server sharing. Performance test engineers may be able to Get better feedback.
In short, the timing of submitting the report needs to be mastered, and there are the following skills:
After the formal performance test is over, the compiled test report should be sent as soon as possible for decision-making and optimization to reflect efficiency.
Between two formal performance tests, several light-weight performance tests can be performed, and the improvement can be informally notified to the whole group, so as to popularize the common sense of performance testing, motivate colleagues and themselves, and improve team spirit.
4. Discussion with the test supervisor
The readers of the performance test report are other colleagues, departments or even higher-level leaders, so it is necessary to discuss the report content with the test supervisor before sending the report. Through discussion, at least the following information can be obtained:
(1) Find the problem. Generally speaking, the test supervisor has more experience in testing and has encountered and solved more problems, so he/she may find the existing reported problems and then put forward suggestions for improvement.
(2) Make the report expression clearer and easier to understand. Generally speaking, the test supervisor has more opportunities to communicate with other colleagues, departments and even higher-level leaders. He has a deeper understanding of the potential readers of the report and is familiar with their reading habits and expressions. If there is more detailed reader information, the report will be clearer and easier to understand if it is revised in a targeted manner.
(3) Increase opportunities for work exchanges. In a team, information sharing is very important. Discussion with the test supervisor can help the supervisor understand the current work and solve some difficulties for the performance test engineer.
In short, it is very beneficial for the growth of a junior performance test engineer to have more work discussions with the test supervisor.
5. Effectively summarize test data
Effectively summarizing test data includes the following key points:
(1) In the content of the test report, the test data cannot be scattered among various parts, but should be listed as a certain part of the document separately. Such an arrangement can make the document structure clearer, and readers can focus more on the data itself when reading the test data.
(2) For the test data, it is impossible to list all the data in the test report, and the data that can best support the conclusion can be listed in one row and the representative meaning of each value can be explained. At the same time, the method of obtaining test data must be listed and clearly stated in as simple a language as possible.
For the test data in the report, the principle we need to grasp is that it must be true and be able to strongly support the conclusion. The test data and test method sections are generally placed in the first half of the report.
6. Combination of test report and chart
It has been mentioned many times before that test reports should be clear and easy to read, and charts are an effective way to enhance readability. For boring data, it is difficult for people to quickly find patterns and trends from the numbers. Once the data is converted into a graph, the situation will be obviously different, and the trend is often very straightforward. In addition, charts with appropriate colors are relatively easier to attract readers' attention.
[Side effects of charts]
However, it should be noted that the more charts, the better, because then the attention that a single chart can attract will be evenly distributed, and finally reduced to the level of text or even lower. There may also be so-called "aesthetic fatigue". factor. Therefore, the chart is not about the number, but about the essence, supporting the conclusion and explaining the problem.
It is very easy to convert data into graphs in Excel, and we will introduce such methods below.
1) Generate a graph for the data in Excel (1)
The method of generating charts for data in Excel actually utilizes the function of the Office Web Component component, which is installed on the hard disk together with Office by default. If you do not find this component in the control panel, you can download it for free from Microsoft's official website.
Finally: The complete software testing video learning tutorial below has been sorted out and uploaded, and friends can get it for free if they need it【保证100%免费】
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can help you too!
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
How to obtain interview documents:
