Defect Tracking Management

Defect tracking management is an important part of the testing work, the purpose of testing is to identify defects in software systems early, so it is an important part of the testing work to track and manage defects and ensure that every defect found is processed in time.
1. The target of defect tracking management
Defects can cause the software to run in an unwanted or unacceptable external behavior results, the software testing process is simply around the defect, the tracking management of defects generally need to achieve the following objectives:
Ensure that every flaw found is resolved; The solution here is not necessarily to be corrected or otherwise handled (for example, in the next version or not), in short, the method of dealing with each bug found must be consistent in the development organization;
Collecting the defect data and identifying the stage of the test process according to the defect trend curve, and deciding whether the test process should end in many ways, it is a common and effective way to determine whether the test process is finished by the defect trend curve.
Collect defect data and conduct data analysis on it as an organization's process wealth.
The first of these is one of the most important, and when it comes to defect-tracking management, the average person will immediately think of this, but it is easy to overlook the second and third goals. In fact, in a well-run organization, the collection and analysis of defect data is very important, from the defect data can get a lot of software quality-related data.
2. Description of the defect
The description of the defect should include the following:

Traceable Information	Defect ID	Unique defect ID that can be used to track defects based on this ID
Basic information about defects	Defect status	Status of defects, divided into "to be assigned", "to be amended", "to be verified", "to Review", "Close"
Defect Title	Title describing the defect
Severity of defects	Describe the severity of the defect, generally divided into "fatal", "serious", "General", "recommended" four kinds
Degree of urgency of the defect	Describe the urgency of the defect, from 1-4,1 is the highest priority level, 4 is the lowest priority level
Defect Submitter	Name of the defective author (e-mail address)
Defect Submission Time	Time of defect submission
Defective Item/Module	The project and module that the defect belongs to, preferably can be positioned to the module accurately
Defect Designation Solution Person	Defect specified by the resolution person, in the defect "submit" status is empty, in the defect "distribution" state by the project manager to specify the relevant developer to modify
Defect specified resolution TIME	The project manager specifies that the developer modifies the deadline of this defect
Defect handlers.	The person who eventually deals with the defect
Defect Processing Result Description	The description of the processing result, if the code is modified, requires that the modification be shown here
Defect processing Time	Time of defect handling
Defect Verifier.	Validation of the Handled defect verification person
Defect Verification Result Description	Description of the validation result (passed, not passed)
Defect Verification Time	Time to verify the defect
Detailed description of the defect		A detailed description of the defect, which is listed separately because the detail of the description of the defect directly affects the developer's modification of the defect, and the description should be as detailed as possible
Test environment Description		Description of the test environment
Necessary Accessories		For some words it is difficult to express a clear defect, the use of pictures and other accessories is necessary

The description of the defect is described in the light purple is the defect in the processing phase filled in the content of the defect is described in the validation phase of the content. In addition to the above description, from a statistical point of view, you can also add "defect introduction Stage", "defect correction workload" and other items.
3, the general process of defect management
The process of defect management is relatively simple, and figure 1 is a defect state diagram.

roles in the process:
1. Test personnel: The person who carries out the test, the initiator of the defect;
2. Project manager: Responsible for the whole project, responsible for the quality of the product;
3, the developer: carry out the development task of the personnel, complete the actual design and coding work;
4, the Evaluation committee: The final confirmation of defects, when the project members of the defect reached a consensus, the exercise of the power of arbitration.
status of the defect
1, initialization: The initial state of the defect;
2, to be allocated: defects waiting to be assigned to the relevant developers to deal with;
3, to be amended: defects waiting for developers to revise;
4, to be verified: The developer has completed the revision, waiting for testing personnel to verify;
5, to be reviewed: Developers refused to modify defects, need to review the Committee review;
6, closed: The defect has been processed to complete.
4. Statistics of defect Data
As mentioned earlier, defect data statistics are also the target of the defect tracking management system. In general, the generated defect data statistical chart includes defect trend map, defect distribution map, defect timely processing statistics and so on.
5. Defect Tracking Management System
The existing defect tracking management software includes Compuware Company's Trackrecord software (commercial software), Mozilla's Buzilla Software (freeware), and the domestic micro-invasive company's BMS software, which feature various features, Can be selected according to the actual situation. Of course, you can also develop bug tracking software yourself, such as developing defect tracking management software based on notes or Clearquese. Our company has developed a note-based defect tracking system, in addition to the above functions, but also through the notes of the mail system to easily send reminders to the relevant personnel (defect processing time-out reminders, defects pending reminders, etc.).
     In addition, as a defect tracking management system, we must also pay attention to the issue of authority assignment. As an important data in the software development process, the defect record cannot be deleted easily, and it cannot be modified arbitrarily for the defects that have been closed. Therefore, the defect tracking management system must set up strict administrative rights, non-related personnel should not take appropriate action, modify the corresponding data. At this point, it is also easy to control through notes.