During Acceptance Testing, ClearQuest is the tool used for communication between the testing team and the development team. The TCO testing team enters defects, the development team resolves the defects, and the testing team verifies and closes the defects. TCO has identified the following Test Severity levels and Test Priority levels:
Test Severity Levels
| | | 1 | Critical | - Testing cannot proceed until the defect has been corrected. The defect is critical enough to crash the system, cause file corruption, or result in potential data loss. - It causes an abnormal return to the operating system, i.e., either a crash occurs, or a system failure message is generated. - The defect causes a program to hang, requiring that the system be re-booted. - It results in a lack of vital program functionality for which there is no work-around. |
|---|
2 | Major | - Although it is unlikely the defect will cripple the system, it does create severe problems, e.g., serious formatting errors, etc. - The lack of functionality resulting from the defect presents major inconvenience to system users. - A work-around exists for the problem, but implementation of that work-around is difficult, complex, and/or inconvenient. - An insufficient or unclear error message appears, resulting in a major negative impact on product use. - The defect prevents other areas of the product from being tested. |
|---|
3 | Average | - While serious in nature, the defect is less severe than a major problem. - A simple work-around for the problem exists. - An insufficient or unclear error message appears, but results in minor negative impact on product use. |
|---|
4 | Minor | - The defect is primarily a cosmetic issue. |
|---|
5 | Enhancement | - The defect is actually a suggestion for improving the application. |
|---|
Test Priority Levels
| | | 1 | Emergency | - The defect must be resolved immediately, both to enable testing of related functions to continue, and to prevent delays in the release schedule. |
|---|
2 | Urgent | - The defect negatively affects application functionality and must be resolved as quickly as possible. |
|---|
3 | Routine | - Although the defect does not halt testing, it should nonetheless be resolved. |
|---|
4 | Low | - The defect does not create a major negative impact on either functionality or application availability. |
|---|
Refer to the Testing and Certification Office Tools page for ClearQuest usage guides. Work with your team's TCO contact to determine when your application will be moved to production. |
|
|
|
