Status and Resolution of issue in Mantis _ test

Classification of bug levels in Mantis (Severity): New features Feature: New types of problems discovered for the first time trivial: minor issues, such as text errors such as button positions in the user interface text: spelling errors on text Unreasonable/awkward tweak: such as: ￥123.345 and other minor errors minor: can not be defined by the above classification, the report is considered to be less serious problem serious error major: Not part of the system crash and deadlock class, but the speaker considered more serious error system crashes crash: System crash-induced error system deadlock block: Description of bug reproducibility in error Mantis causing system deadlock (reproducibility): Always always: Every attempt will occur sometimes sometimes: relative to the following "random" frequency to High number of random random not tested have not tried: the action that found the bug was only one time unable to reproduce unable to reproduce: Only one time, after which no attempt can reproduce. N/A: not appli Cable/acceptable the ability to make a bug when you try again is not a description of the bug priority in Mantis: None: The related bug has resolve nonexistent or feel that priority is not necessary to embody low: low-priority, left to final resolution, if item The goal is very tight. Normal: Medium priority High: immediate and urgent priority bugs will be modified after the bug has been modified the emergency urgent: must be modified within one or a day urgent immed Iate: Need to immediately change the description: The priority and the level of the bug itself is not exactly the same, such as some bugs are serious errors, but only once in a while, do not affect the normal use of software, such a bug can be properly prioritized to reduce the priority, While some bugs are not serious errors, but it has always been, the users of the software caused a greater disturbance, such a bug will be appropriate to improve the priority according to the situation, that is, the priority of the bug can be considered above the severity (severity level) and reproducibility 　　　　A comprehensive consideration of (frequency of occurrence). Of course, the problem of priority choice is very much related to the understanding of reporter itself, different repoRter may choose a different priority for the same bug, mainly based on their own experience and understanding to make a more appropriate selection of mantis status and resolution status (resolution) description Status: New NEW: When a tester reports a new bug and does not assign it to a specific developer when it is modified feedback: The developer thinks that the bug does not need to be modified and feeds it back. 　　　　After discussing the evaluation, the tester and the developer decide whether to turn it off as a recognized acknowledged: The bug appears in most modules or on the page and is set to acknowledged (confirmed by the developer) 　　　　Confirmed confirmed: Developer (QA) confirms that the bug exists and is ready to modify it to confirmed assigned assigned: After assigning a new bug to a specified developer, the status becomes assigned (typically done by the project manager) Resolved Resolved: Developer (QA) confirms that the bug has been resolved and that the tester can verify the test has been turned off closed: Confirm the bug has been resolved, shutdown resolved: The unhandled open:bug has not been resolved the modification of the Fixed:bug has been registered and The test reopened Reopen:bug was once resolved, but the solution was considered incorrect and could not be reproduced unable to reproduce: Unable to reproduce, the assigned developer would like to reproduce the bug when it was found that the bug could not be reproduced when the bugs were Resolut Ion set to this item cannot fix the not fixable: cannot fix this bug repeat problem duplicate: Duplicate a bug that already exists is not a problem no change required: Managers and related developers after the requirements and design verification, decided not to To modify the pause suspended: Deferred, generally refers to the current version does not make changes, the next version of the solution does not make changes won ' t fix: Not ready to modify this bug description: The status is mainly QA to set the modification, and resolution is the relevant developer And the project manager to make the changes. But not exactly, there are several intersecting items, such as "callback" in status, where the developer or project manager sets the bug to a state when the bug is not understood and the resolution is "reopen" It should be QA after testing the relevant solution found that it is not correct and willResolution modified to open again. QA: The abbreviation of the English quality assurance, the Chinese meaning is the quality assurance, its definition in iso8402:1994 is "to provide enough trust to show that the entity can meet the quality requirements, All planned and systematic activities carried out in the quality management system and confirmed as required. Some organizations that carry out ISO9000 will set up such a department or post to be responsible for the quality assurance functions required by the ISO9000 standards, and the people who hold such jobs are called QA personnel.