Bug report

Bug Report

A bug report or defect report is a document that describes a situation or a sequence of actions that led to the incorrect operation of the test object, indicating the reasons and the expected result.
For more detailed information about a bug report, we recommend that you pay attention to the following information, after reading which you will get a comprehensive understanding of the structure, writing features and some other nuances necessary for writing good bug reports:

Structure of Bug Report

We offer you a comment from one developer – after reading the short description of the bug (Bug Summary), I must understand the problem; after reading the detailed description (Bug Description), I must know the line of code to edit.

You can agree or disagree with this, but the meaning of this statement is that you should do everything so that you have fewer questions on the merits of the problem described in the bug report. Since each bug report returned to you with the status “Rejected”, “Not reproduced”, “Required information” (Rejected, Can’t Reproduce, More info) is a waste of time, both for you and the developer. And time, as you know, is the money that we get for doing our job the best!

We are sure that if you use all the recommendations we have proposed in the future, then the quality of your bug reports will be at a high level, and in the work process, you will have minor complaints from managers and developers.

Example of Simple Bug Report:

ActionExpected ResultActual Result
Login with admin userThe user is logged in as an admin.The user is logged in with guest rights.

Description of defect: When you try to login as Admin User, you are logged in as Guest.

Steps to Reproduce:

Actual Result: Logged in as a Guest.

Expected Result: Logged in as Admin.

Attachments and test data can be added to Bug Reports; it will help Developers find the defect’s root cause.