Bug Report - Best Practices

Question 1

What is a bug report?

Answer 1

It is a document that includes all information about a software error.

Question 2

What is the bug title, bug ID, and severity?

Answer 2

Bug title - Short summary of what went wrong and where it happened

Bug ID - ID that is usually automatically assigned by bug tracking system

Severity - Describes how severe the impact of the error is to the system

Question 3

What is the priority, assigned to, and reported by?

Answer 3

Priority - The order in which the problem should be fixed

Assigned to - Name of the person that should work on the bug

Reported by - Name of the person reporting the bug

Question 4

What is the status, environment, and steps to reproduce?

Answer 4

Status - the current status of the bug

Environment - All information about the system used during testing

Steps to reproduce - list of step by step instructions for developer to follow

Question 5

What is expected result and actual result?

Answer 5

Expected result - Explanation of what we expect to see if there was no bug

Actual result - Explanation of the result that actually happened

Question 6

What is the rule of the 3 W’s to write bug reports?

Answer 6

1. WHAT happened
2. WHERE did it happen
3. WHEN (under WHICH circumstances)

Question 7

What is the bug life cycle?

Answer 7

1. New
2. Assigned
3. Resolved
4. Closed or Reopened