On the run database
Introduction
The basis of the tester is not only detected, but in a clear, accessible description of the perception of the bug. We will not dwell on the software used for this purpose.
The purpose of this article – to give an indicative list of Status, Priority, and Severity, which accompany each described by a bug.
Status
- Added – this status have the feature request, that have been made by the developer at the request of a beta-tester. Prior status: new, in process, deferred, delegated, re-do, searching conditions, updated.
- Cannot Verify – the status of those bugs that were fixed by the developer, but can not be tested a beta tester for several reasons (for example, the bug has been described by the developer, but not reproduced on a beta-tester machine, due to differences in hardware computer configurations, so after the patch it can not be tested a beta tester, so as not reproduced above). Prior status: added, fixed.
- Could Not Duplicate – the status of the bug, which is produced from beta testers, but not reproduced in the developer (or vice versa) for several reasons. Prior status: new, updated.
- Deferred – fix a bug postponed until a new version, update, or a specific / indefinite period. Prior status: any.
- Delegated – correction requested a specific person (the developer). Prior status: any.
- Fixed – bug fixes. Prior status: new, in process, deferred, delegated, re-do, searching conditions, updated.
- In Process – bug (or feature) are described, the message is read by the developer, understood (or discussed), work on the bug is in the process. Prior status: new, searching conditions, updated, re-do.
- New – new, just introduced a beta tester (developer) bug, the conditions of play is clearly described, ie bug occurs steadily during the passage of certain steps (steps to recreate). Prior status: he is the previous status of most bugs.
- No longer relevant – a bug that no longer needs to be rectified. Prior status: any.
- Re-do – a bug that has been declared as fixed (or a feature, launched as added), which has appeared when testing is not amended as a consequence of various reasons: Previous status: added, fixed.
- Searching Conditions – a bug, whose appearance was registered beta tester, but the conditions of its reproduction are not clear. Further work is required to stabilize the conditions of reproduction of the bug. Can be "understood" by the developer with additional testing tools (logs, tools, plugs) or knowledge of the program code responsible for generating the bug. Prior status: new, cannot duplicate, but in most cases the original status yavlyatsya described bug.
- Updated – information about the bug (or fiche), supplemented with new facts of its origin, which may help a developer in his playing, the search area code and the "neutralization". Prior status: any.
- Verified – the status of those bugs that were fixed by the developer and rechecked a beta tester. Prior status: added, fixed. Will not be fixed – a bug which, for various reasons can not be corrected by the responsible developer. Prior status: new, in process, updated, searching conditions.
- Not a bug – what is described as a bug really is not. Typically this applies to those features of the program that have not been described in the documentation as its features and / or were perceived as a beta tester bugs. Benefit status for writing Help and FAQ in the future if necessary.
Priority
- Normal – the priority of this bug (or features) is normal (assessed by the urgency of correcting the developer). Corrected in order the main line. Something between Low and High.
- Low – low priority, does not require an immediate fix, perhaps, "delay" correction for a certain period of time. Something between VeryLow and Normal.
- High – require an urgent, but not an immediate fix. Corrected in the absence of bugs with status VeryHigh. Something between Normal and VeryHigh. For example, a bug with Severity – Critical.
- VeryLow – a very low priority, does not require an immediate fix, perhaps, "delay" correction for an indefinite period. The lowest priority. Bugs with this priority are fixed at last.
- VeryHigh – requires immediate correction. The highest priority. Bugs with this priority are corrected first. For example, a bug with Severity – Causes crash.
Severity
- Causes crash – a bug that crashes the system. Points to the inefficiency of the program, requires an immediate fix.
- Cosmetic – a bug, which is a cosmetic defect (for example, line color, different from the proper, another font, grammatical and spelling errors, etc.)
- Critical – a bug that leads to disruption of the program, but "no touch" system as a whole.
- Error Handling – bug in handling errors. T Functional – a bug in the program’s functionality.
- Minor – not classifiable bug or glitch, doubtful – usually reflects the lack of a full document.
- Setup – a bug that occurs during the installation of the program or its corollary.
- Suggestion – a proposal to improve quality.
See Also