Bug description, rating and life cycle

How to describe a bug

1. Find the problem version

2. The environment in which the problem arises

3. Steps for error recurrence ： Describe the shortest steps for problem recurrence

4. A description of the expected behavior

5. Description of the wrong behavior

6. Other requirements （ For example, fault classification, etc ）

bug To rank

1.Blocker（ collapse ）

2. Critical（ serious ）

3.Major（ commonly ）

4.Minor（ secondary ）

 

bug Life cycle of （open—closed）

• New： Newly discovered bug, Decide whether to assign developers to modify without review

• Open： Confirmation is bug, And think it needs to be modified , Assign to the appropriate Developer

• Fixed： After the developer makes the modification, it is marked as the modification status , To be verified by regression test of testers

• Rejected： If not bug, Refuse to modify

• Delay： If you think it doesn't need to be modified or can't be modified for the time being , Modify later

• Closed： Modify the state of bug The regression verification by the tester passed , Then close bug

• Reopen： If verified bug There is still , You need to reopen bug, Revised by the developer group

    

     invalid bug：open->closed   open->rejected->closed