B2G/QA/Triage: Difference between revisions
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
When QA support is needed on the bug, but none of the above keywords apply. When this keyword is used, the person flagging qawanted needs to indicate what QA support is needed. | When QA support is needed on the bug, but none of the above keywords apply. When this keyword is used, the person flagging qawanted needs to indicate what QA support is needed. | ||
== QA Contact == | |||
<Describe use of the field here - including how it's set, sheriff exceptional cases, etc> | |||
== Priorities == | |||
<Describe priorities for the bugs flagged with the keywords above> | |||
== Queries == | |||
<List off the major relevant queries for b2g> | |||
Revision as of 00:06, 27 February 2013
Overview
This document provides a summary of how we manage requests for QA support through bugzilla, more specifically for the B2G QA team.
Summary of Keywords
Note: Only one keyword should be used optimally to represent what is needed by QA.
steps-wanted
When reproducible steps to reproduce are needed for a certain bug.
testcase-wanted
When a reduced test case is needed for a certain bug.
regressionwindow-wanted
When a regression range is necessary to identify a first good build and first bad build for a particular bug.
verifyme
When a verification of a bug is needed to ensure that the patch on the bug actually fixed the problem.
qawanted
When QA support is needed on the bug, but none of the above keywords apply. When this keyword is used, the person flagging qawanted needs to indicate what QA support is needed.
QA Contact
<Describe use of the field here - including how it's set, sheriff exceptional cases, etc>
Priorities
<Describe priorities for the bugs flagged with the keywords above>
Queries
<List off the major relevant queries for b2g>