Write efficient defect reports

Defect report is an important communication bridge between test engineer and development engineer , It is also an important output of test engineer's daily work . As a good test engineer , One of the most basic skills is , Express the defects accurately and unambiguously . The defect report not only reflects the professionalism of the test engineer , Its own quality has a direct impact on the speed of defect repair and the work efficiency of development engineers , It affects the credit of Test Engineers , Test the effectiveness of collaboration with developers .

1. title

The title should describe the nature of the problem as much as possible , And avoid staying on the surface of the problem （ The title should not be too long ）

2. Defect Overview

Defect overview usually provides more general description of defect nature and phenomenon

3. Defect effect

4. Priority and severity

5. Environment configuration

It is used to describe the configuration details of the test environment in detail , Provide necessary environmental information for defect recurrence .

6. The attachment

Attachments usually provide necessary evidence to support the existence of defects , Common attachments are screenshots of the interface 、 Test case log 、 Server side day Records 、GUI Test execution video, etc . For those that are hard to describe in words GUI Defects in interface layout . You can submit a defect report by taking a screenshot and highlighting the area of interest , Special note , The screen capture must be full screen , such as web Interface , hold bug When it appears url route , Click back and forth , The whole screen capture is clearly marked .

Geek college study notes