Software defect Management Process

Software defects (bugs) can cause an unwanted or unacceptable external behavior result when the software is run, and the process of software testing is simply about defects. In order to effectively track and manage the situation of the bug, instruct the Test team and developers to effectively deal with related bugs, it is necessary to adopt a complete set of methods and means to manage it, that is, this article will introduce the defect management process.

First, the cause of the defect

Software errors and software defects that are commonly described by development and testers are two different concepts, in short, software errors are human errors that are not expected or visible during the software declaration cycle, resulting in software defects. In the process of software dynamic operation, the software defect is exposed in some condition, which leads to the failure of software.

Causes of software defects:

① the lack of comprehensive, incomplete and inaccurate preparation of the requirements specification;

② design changes, no timely communication or communication is not smooth;

③ requirements change in the development process;

④ the developer of the program does not understand or understand the business of the inconsistency;

⑤ code writing is not rigorous, missing commas, the divisor is 0, etc.

⑥ the software and hardware environment of the system.

A correct understanding of the definition and source of defects can help testers to find ways to judge defects easily, so the user's requirement specification or product specification is the key to judging the defect. Therefore, in the process of identifying defects, testers can start from the following aspects:

① first testers should be very familiar with explanatory documents such as requirements Specification or product specification, as these documents reflect the actual business needs of the users;

② to discover neglected issues by understanding the industry and business background of the products or systems being tested;

③ through their own continuous accumulation of testing experience and industry rules, found deep-seated defects;

④ through communication to collect, learn and share other people's methods of judging defects.

Ii. Introduction of Defect Report

The defect report is the main product of the test engineer and one of the main deliverables of the Test team. Its role is to enable developers to understand how defects are produced and to facilitate better repair of defects.

The major elements of defect reporting are: Defect title, module of defect occurrence, function point of defect, defect type, defect status, detailed steps of defect, severity of defect, priority of defect, status of defect, software version involved, person submitting defect, date of submission. You can also provide the associated test case number.

Information to fill out after the defect has been processed: The version number of the fix, the person who repaired it, the Reject/suspend person.

Third, the defect management process

① Overall process

② Defect Submission Process

③ Defect Repair Process

④ Defect Verification Process

⑤ defect Rejection Process

⑥ Hang defect processing flow

⑦ dispute defect Handling process

Software defect Management Process