All defects are not the same type. Some defects can lead to method failure. Some defects can be mild (eg, a spelling mistake in error message). Thus, the defects must be classified according to its impact on the functionality of the application. Defects can be classified as
-Blocker: Blocks development and / or test work, production could not run.
-Critical: critical defects lead to a method crash, or your order may not be usable at all if this type of defect occurs. In an application time-critical, time is not within the limits or if the response time is not within the limits, then it may even be often called the critical defect. Inconsistent performance of the application is also critical defect.
-Major: major loss function. Major defects won't lead to a crash, but may lead to some parts of the application hard to make use of, such as navigation menus difficult.
: Do not block any functionality to be tested however, is an important issues for further. Normal
-Minor: Minor loss of function or any other issue with this solution is simple. Minor defects can be tolerated, as the shortage of help for some functions; a spelling mistake in a mistake message is incorrect order of the control buttons on a graphical user interface, etc.
-Trivial: cosmetic issue like misspelled words or misaligned text.
In the work of the recording of the defects of a log sheet of defects, the severity of the defects ought to even be noted. If a critical defect is present in the code, then the application is not prepared for delivery. Only a few major flaws allowed. Similarly, a threshold must be kept on the number of minor defects. On the threshold depends on the application, the project manager / test team member must use his trial in fixing the threshold of major and minor defects.
After analyzing the test document, test director needs to pick if the application is prepared for delivery or not.