On defect description style

As long as you are engaged in testing , It will involve the link of raising defects , How can we describe defects , Here are two defect description styles with and without attachments .

One 、 No attachment style ：

explain ：

1. Product module is required

2. The affected version is the current test version , By testers in the project > In the version add to .

3. The current assignment refers to the person responsible for developing this module .

4. The test title is given by : route + operation + result + Reproduce the situation （100% Reproduce without writing ）, Unrepeatable master （ Can't reproduce ）, If the recurrence probability is relatively small, write down the approximate recurrence probability （ Recurrence probability X%）

5. When it comes to browser compatibility, you must choose the browser used when testing defects .

6. The severity level of defects must be selected according to the requirements of defect management documents .

Two 、 There are attachment styles

explain ：

1. Product module is required

2. The affected version is the current test version , By testers in the project > In the version add to .

3. The current assignment refers to the person responsible for developing this module .

4. The test title is given by : route + operation + Problem specification + Reproduce the situation （100% Reproduce without writing ）, Unrepeatable master （ Can't reproduce ）, If the recurrence probability is relatively small, write down the approximate recurrence probability （ Recurrence probability X%）

5. When it comes to browser compatibility, you must choose the browser used when testing defects .

6. Defects of accessories , It is not necessary to describe the results when reproducing the steps .

7. The severity level of defects must be selected according to the requirements of defect management documents .