Shulou(Shulou.com)06/02 Report--

The following is an excerpt from the book "Xiaoqiang Software testing Crazy handout-performance and Automation"

If it is of any help to you, you are welcome to forward this article

After the analysis is finished, we will write a report. In this era of highly developed Internet information, we are used to "reaching for food and clothing" and "picking up a pen and forgetting words". Let alone write a test report, or even write two sentences and don't even know how to write. It can be seen that the more developed the information technology is, the more people should strengthen the cultivation of writing ability.

It is relatively important to write a beautiful report. The key is to master the core ideas of writing a report. I usually follow a few main points when writing it:

1) the structure is clear: it is necessary to have a good sense of hierarchy so that it will not look messy and easy to understand. Don't be too confused.

2) concise description: don't write too much nonsense, sometimes the process of analysis is very long, but you can do appropriate cutting when writing, do not write a rigid word, who has time to read an ultra-long report.

3) mixed picture and text: again, a picture is worth a thousand words. Don't write a paragraph if you can explain it clearly with a picture.

4) data comparison: the most powerful report is not the hype described, nor is it much literature and art, but there are data and comparison, so that it is more persuasive.

Now that we know the guidelines for writing a good report, let's take a look at the most frequently asked question: "what's the format of the report?" . There are two common report formats, which you can refer to when writing:

1) the conclusion comes first: it means that I write out the final analysis results at the beginning of the report, so that the friends who read the report can see it at a glance, and there is no need to look down one by one.

2) after the conclusion: as the name implies, the conclusion is put at the end, similar to the "current account", analyzed step by step according to the order, and finally gives the conclusion.

There is no absolute good or bad between these two formats, you can choose them according to the actual situation.

In addition to the above considerations, there are also some details worth considering:

1) write different test reports for different people.

For example, the reports given to leaders and technicians are completely different, their concerns and professionalism will be very different, and perhaps a proud report will be criticized for being worthless because it is given to the wrong person. If the report is sent to the leader, try to avoid test terminology and describe it in words that are easier to understand. The report should be concise and powerful, and don't make too many useless descriptions, because leaders don't have time to pay attention to details, they care more about conclusions. If the report is sent to a technician, you can ignore the above concerns and write it from a professional and technical point of view, reflecting the analysis process, details, solutions, and conclusions.

2) give the appropriate solution.

For the analysis of the problem, should be given an appropriate solution, some friends may feel unable to give a solution will be very "embarrassed", in fact, no. Its own performance testing is a huge and complex project, which can not be completed by one person. It needs the cooperation and assistance of various personnel, and everyone can accomplish what they are good at. And for test engineers, this process is more meaningful, you can learn different knowledge, get different solutions to different problems, for you is a valuable "wealth"!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.