25 | Defect Report

Published on Aug 17, 2021 | By Tesvan team

Defect report


is a document that identifies and describes a defect detected by a tester. The purpose of a defect report is to state the problem as clearly as possible so that developers can replicate the defect easily and fix it.


Defect Report Template

In most companies, a defect reporting tool is used and the elements of a report can vary. However, in general, a defect report can consist of the following elements.

While reporting the bug to developer, your Bug Report should contain the following information

  • Defect_ID - Unique identification number for the defect.
  • Defect Description - Detailed description of the Defect including information about the module in which Defect was found.
  • Version - Version of the application in which defect was found.
  • Steps - Detailed steps along with screenshots with which the developer can reproduce the defects.
  • Date Raised - Date when the defect is raised
  • Reference - where in you Provide reference to the documents like. requirements, design, architecture or maybe even screenshots of the error to help understand the defect
  • Detected By - Name/ID of the tester who raised the defect
  • Status - Status of the defect, more on this later
  • Fixed by - Name/ID of the developer who fixed it
  • Date Closed - Date when the defect is closed
  • Severity which describes the impact of the defect on the application
  • Priority which is related to defect fixing urgency. Severity Priority could be High/Medium/Low based on the impact urgency at which the defect should be fixed respectively


Reporting Defects Effectively

Be specific:

  • Specify the exact action: Do not say something like ‘Select ButtonB’. Do you mean ‘Click ButtonB’ or ‘Press ALT+B’ or ‘Focus on ButtonB and click ENTER’? Of course, if the defect can be arrived at by using all the three ways, it’s okay to use a generic term as ‘Select’ but bear in mind that you might just get the fix for the ‘Click ButtonB’ scenario.
  • In case of multiple paths, mention the exact path you followed: Do not say something like “If you do ‘A and X’ or ‘B and Y’ or ‘C and Z’, you get D.” Understanding all the paths at once will be difficult. Instead, say “Do ‘A and X’ and you get D.” You can, of course, mention elsewhere in the report that “D can also be got if you do ‘B and Y’ or ‘C and Z’.”
  • Do not use vague pronouns: Do not say something like “In ApplicationA, open X, Y, and Z, and then close it.” What does the ‘it’ stand for? ‘Z’ or, ‘Y’, or ‘X’ or ‘ApplicationA’?”

Be detailed:

  • Provide more information (not less). In other words, do not be lazy. Developers may or may not use all the information you provide but they sure do not want to beg you for any information you have missed.

Be objective:

  • Do not make subjective statements like “This is a lousy application” or “You fixed it real bad.”
  • Stick to the facts and avoid the emotions.
  • Reproduce the defect:
  • Do not be impatient and file a defect report as soon as you uncover a defect. Replicate it at least once more to be sure. (If you cannot replicate it again, try recalling the exact test condition and keep trying. However, if you cannot replicate it again after many trials, finally submit the report for further investigation, stating that you are unable to reproduce the defect anymore and providing any evidence of the defect if you had gathered.)

Review the report:

  • Do not hit ‘Submit’ as soon as you write the report. Review it at least once. Remove any typos.



Useful links
1. Bug report article/eng/
2. Bug report video tutorial/rus/
3. Bug report video tutorial/eng/
4. Bug, Bug report video tutorial/arm/

Next Lessons

26 | Test Case

Aug 18, 2021

A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The p...

By Tesvan team

27 | Test Script

Aug 18, 2021

Test Script A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the ...

By Tesvan team

28 | Test Plan

Aug 18, 2021

A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project.Test Plan tem...

By Tesvan team

29 | Agile model

Aug 18, 2021

Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile...

By Tesvan team

30 | Agile VS Waterfall

Aug 18, 2021

Agile VS Waterfall Key Difference    Useful links1. Agile vs Waterfall article/eng/2. Agile vs Waterfall article/rus/3. Agile vs Waterfall video tutorial/eng/4....

By Tesvan team

Interesting For You

12 | Black-box testing

Aug 13, 2021 | By Tesvan team

Black Box method Black Box Testing is a software testing method in which the functionalities of software applications are tested without having knowledge of int...

01 | Quality Assurance

Aug 09, 2021 | By Tesvan team

Quality Assurance VS Quality ControlQuality assurance and quality control are two aspects of quality management. While some quality assurance and quality contro...