What is defect logging and tracking?

Defect logging is simply finding bugs and defects in the application that is being tested. The testing team checks for potential issues and logs the defects along with their status and priority before assigning it to the development team.

Once a defect is detected, defect tracking manages those defects. A defect tracking managing system evaluates and handles the multitude of defects that accumulate over time and effectively manages them.

The following illustration demonstrates a simple defect logging cycle; however, more elaborate cycles are possible. A team member finds a bug and logs information about it, then reports it to another member. The second member resolves the bug, and the submitter verifies that the defect is fixed.

Guidelines for defect tracking

The following methods guide the process of defect tracking:

• Information capture: Aquire the basic information to begin the process of debugging.
• Reproduce bugs: Reproduce the past defects to determine how defects occur.
• Prioritize: Prioritize and schedule a task depending on its severity and importance.
• Communicate: Communicate who is fixing and creating the defect.
• Environment: Test the application on different combinations of software and hardware environments for defect analysis.

Defect tracking parameters

1. Defect ID: The unique ID of a defect.
2. Priority: The priority of a defect, depending on its severity.
3. Created by: The person who detects the defect.
4. Created date: The date on which the defect is detected.
5. Assigned to: The person who is responsible for fixing the defect.
6. Resolved date: The date on which the defect is fixed.
7. Resolved by: The person who fixes the defect.
8. Status: Status of the defect that indicates if it is fixed or not.