Effective Bug Report: Difference between revisions
No edit summary |
|||
| Line 37: | Line 37: | ||
=Preconditions= | =Preconditions= | ||
=Steps to reproduce | =Steps to reproduce= | ||
=Expected Result= | =Expected Result= | ||
Revision as of 19:41, 15 June 2023
An effective bug report should contain the following:
Bug ID
Title/Summary
Preconditions
Steps to reproduce
Expected Result
Actual Result
Attachments (visual proofs of bug such as screenshots, videos, logs)
Environment
Severity/Priority
Status
Date of creation
Additional information about a bug can be added if needed
Bug ID
Each bug should be given a unique identification number. Bug reporting tools automatically provide a unique number to the newly raised bugs. This field helps to identify the bug easily.
Title/Summary
A summary of the issue should be provided. The summary should be a concise statement that helps to identify the problem. Bug titles should be easy to understand, which would help identify the issue quickly. Try to briefly answer 3 questions: "What? Where? When?"