In the process of software testing, each company has formulated a software defect handling process. Each company's software defect handling process is different, but the most basic process they follow is the same, which must go through submission, distribution, confirmation, and processing. , retesting, closing and other links, as shown in Figure 1.
Defect Handling Process
The specific explanation of the software defect processing link shown in Figure 1 is as follows.
(1) Submit: After the tester discovers the defect, he submits the defect to the test team leader.
(2) Assignment: After the test team leader receives the defects submitted by the testers, he will hand them over to the developers.
(3) Confirmation: After receiving the handed-over defect, the developer will discuss with the team and even the testers to determine whether the defect is a defect.
(4) Rejection/Postponement: If after negotiation, the defect is not a real defect, then refuse to deal with it, and close the defect; if after negotiation, it is determined that it is a real defect, you can choose according to the severity or priority of the defect, etc. Immediate processing or deferred processing.
(5) Processing: The developer modifies the defect.
(6) Retesting: After the developer has modified the defect, the tester will retest (retest) to check whether the defect has indeed been modified. If it was not corrected, resubmit the defect.
(7) Closing: After the tester retests, if the defect has been corrected, the defect will be closed, and the entire defect processing is completed.
Software Defect Report
In the actual software testing process, when submitting the software test results, the testers will record the details of the defects according to the company's specified template (Word, Excel, defect management software, etc.) to generate a defect report. Each company's defect report template and It is not the same, but generally includes the number, type, severity, priority, test environment, etc. of the defect, and sometimes there are suggestions from testers.
If there is a defect in the login function of a piece of software (the software name is "Handheld Q&A"), and the tester finds that when the user name entered exceeds 10 characters, he cannot log in during the test. For such a defect, report it according to the company's defect report. The template makes a defect report, as shown in Table 1.
bug report
Keep the following in mind when writing defect reports.
(1) Each defect has a unique number, which is the identification of the defect.
(2) Defects must have steps to reproduce.
(3) A defect generates a report.
(4) The defect report should be neat and complete.