Defect level classification
Fatal: The test process crashes, the system crashes, the data drops, and the function is not implemented
Critical: lead to software function instability, function implementation error, process error
General: check errors, rare faults, typos, do not affect the function, affect the experience
Low-level: minor issues that have no impact
Defect report composition
Defect title
The module to which the defect belongs,
the version of the defect found,
who is assigned to deal with it
, the status of the
defect, the severity of the defect
Defect life cycle
Smoothly
Test discovery
Create defect report, assign development,
develop repair, refer back to test,
test verification, close defect
In the case of unsuccessful
development, point back to the test after the development and repair, and the test verifies that the repair is not successful, point back to the repair again
Can all software defects be repaired, and should they be repaired?
Theoretically, software defects can be repaired, but some repair costs are relatively high, and the perfection of the software cannot be pursued. Determine whether to repair the defects according to the risk.
1. Insufficient time, not enough time in the project to modify the defects may lead to other defects, resulting in the delay of the project
2. Some defects only appear in special circumstances, such defects can be placed in future versions for the benefit of the project Perform repair and upgrade
3. Defects that are not defects. Whether to modify the defect should be discussed and decided by the tester, project manager, and programmer to ensure the normal operation of the project