Software testers, how to mention bugs?

Novice Test Engineer submit bug common problem ： Unclear understanding of requirements 、 Yes bug Inaccurate positioning 、 Unclear problem description, etc .

that , How can software testers improve Bug?

bug The submission is mainly divided into three parts ： title 、 essential information 、 describe .

1. title

[ Problem side ][ General description ]

2. essential information

The seriousness of the problem ： The more serious the problem, the priority should be given to

Question priority ： High priority issues will be dealt with first

bug Type：bug type

Assigned user （ I.e. introduction bug Development of ）

Related items ： Linked to a specific project , Later can be used for analysis

Associated development （ I.e. introduction bug Development of ）

3. describe

a. Relevant test data

For example, test account 、 Page Jump links and other test data .

b. Scene description ： How to describe a scene is very important , It is also the key factor to determine whether the development can be positioned quickly

Sort out what kind of operation caused the problem

Try again to reproduce according to the steps we combed , Describe the operation according to each step

After the scene description is completed , The expected results and actual results need to be described or displayed

c. Related screenshots

ui A screenshot of the page

Screenshot of interface error report

Log related screenshots

db Screenshots of the results, etc

When we found the problem , The first thing to do is to confirm whether it is caused by the non-standard of our own testing . If you're not sure , You can try to reproduce again .bug The description must be specific , Otherwise, it will not only waste time , It's also inefficient . Of course, if some bug Not very descriptive , And when the cost of face-to-face communication is the lowest , We can choose the way with lower cost .