Defect Reporting

Defect reporting is an important part of the software testing process, as it helps identify and track defects in the software being developed. The following is a general defect reporting process that can be used in software testing:

Identification: A tester identifies a defect in the software being tested.

Reproduction: The tester reproduces the defect to ensure that it is not a one-time occurrence.

Classification: The tester classifies the defect based on its severity, priority, and type. Severity refers to the impact of the defect on the system, priority refers to the urgency of fixing the defect, and type refers to the nature of the defect (e.g., functional, performance).

Documentation: The tester documents the defect by creating a defect report. The report should include information such as the steps to reproduce the defect, the expected behavior, the actual behavior, the environment in which the defect occurred, and any other relevant information.

Reporting: The tester reports the defect to the development team responsible for fixing the defect. This can be done through a defect tracking tool or by sending an email to the development team.

Verification: The development team verifies the defect by reproducing it, analyzing it, and determining the root cause of the defect.

Resolution: The development team fixes the defect and re-tests the software to ensure that the defect has been resolved.

Closure: Once the defect has been fixed and verified, the tester verifies the resolution and closes the defect report.

It is important to note that the defect reporting process may vary depending on the organization's testing processes and the tools used for defect tracking and management. However, the overall goal is to ensure that defects are identified, documented, and resolved in a timely and efficient manner to ensure the quality of the software being developed.

Firstly, we have to know Software Application Life Cycle, in this there are 3 phases –
1) Development phase-
In this phase developers find any mistake; they called it as mistake.
2) Testing phase-
In this phase if testers find any mistake, they called it as bug or defect or error of fault.
3) Production phase-
In this phase if end user finds any mistake, they called it as failure.


Defect Management:

Defect tracking, defect reporting is called it as a defect management. Some companies are uses excel and some companies may use tools for defect management. For ex – Bugzilla, Mantis, Issue tracker, QC, etc.


Defect Report Template:

1) Defect ID: Unique name for identifying the defect.
2) Defect Description: Details about the defect
3) Test case ID: Test case ID for tracking
4) Product Version: Version of the product
5) Build Version: Version of the build
6) Priority: Importance of the defect
7) Severity: Based on functionality importance
8) Screen shots: jpg/png
9) Status: status of defect
10) Reproducible: Yes / No
11) Tester name: ABC
12) Assign to: Corresponding developer
13) Remark: Optional


Defect Reporting Process:
In small scale companies: Tester -> Developer
Middle scale / Large scale companies: Tester -> Test lead -> Developer lead -> Developer


Defect Life Cycle: 
Flow of defect life cycle
1) New -> Open -> Fixed -> closed
2) New -> Open -> Rejected -> Closed
3) New -> Open -> Fixed -> Re-open ->  Fixed -> Closed
4) New -> Open -> Rejected -> Re-open -> Closed
5) New -> Open -> Deferred


Severity: Depends on company strategy

Levels of Severity –
5 Level (Middle and Large scale) -> Urgent, Very high, High, Medium, Low
3 Levels (Small scale)-> High, Medium, Low



Priority: Depends on company strategy
Levels of Priority –
5 Level (Middle and Large scale) -> Urgent, Very high, High, Medium, Low
3 Levels (Small scale) -> High, Medium, Low