 |
 |
 |
All defects are not of the same type. Some defects may result in system crash. Some defects may be very minor (such as a spelling mistake in an error message). So, the defects need to be classified based on its impact on the functionality of the software. The defects can be classified as -
Blocker - Blocks development and/or testing work, production could not run.
Critical - Critical defects result in a system crash, or the application may not be useable at all if this type of defect occurs. In a time critical application, if the timing is not within the limits or if the response time is not within limits; then also the defect can be termed as critical. Inconsistent performance of the application is also a critical defect.
Major - Major loss of function. Major defects will not lead to a system crash, but may result in some portions of the application difficult to use, such as difficult navigation of the menus.
Normal - Not blocking any functionality to be tested however it is an improtant issues to track
Minor - Minor loss of function, or other problem where easy workaround is present. Minor defects can be tolerated, such as lack of help for some functionality, a spelling mistake in an error message, incorrect ordering of control buttons in a GUI etc.
Trivial - Cosmetic problem like misspelt words or misaligned text.
While recording the defects in a defect log sheet, the severity of the defects also needs to be noted down. If a critical defect is present in the code, then the software is not ready for delivery. Only few major defects are allowed. Similarly, a threshold needs to be kept on the number of minor defects. As the threshold depends on the application, the project manager/test team member has to use his judgement in fixing the thresholds on major and minor defects.
After analyzing the test report, the test manager needs to decide whether the software is ready for delivery or not.
Blocker - Blocks development and/or testing work, production could not run.
Critical - Critical defects result in a system crash, or the application may not be useable at all if this type of defect occurs. In a time critical application, if the timing is not within the limits or if the response time is not within limits; then also the defect can be termed as critical. Inconsistent performance of the application is also a critical defect.
Major - Major loss of function. Major defects will not lead to a system crash, but may result in some portions of the application difficult to use, such as difficult navigation of the menus.
Normal - Not blocking any functionality to be tested however it is an improtant issues to track
Minor - Minor loss of function, or other problem where easy workaround is present. Minor defects can be tolerated, such as lack of help for some functionality, a spelling mistake in an error message, incorrect ordering of control buttons in a GUI etc.
Trivial - Cosmetic problem like misspelt words or misaligned text.
While recording the defects in a defect log sheet, the severity of the defects also needs to be noted down. If a critical defect is present in the code, then the software is not ready for delivery. Only few major defects are allowed. Similarly, a threshold needs to be kept on the number of minor defects. As the threshold depends on the application, the project manager/test team member has to use his judgement in fixing the thresholds on major and minor defects.
After analyzing the test report, the test manager needs to decide whether the software is ready for delivery or not.
| ■ | Blocker |
| ■ | Critical |
| ■ | Major |
| ■ | Normal |
| ■ | Minor |
| ■ | Trivial |
Defect Classification