QA/WhiteboardTags

< QA
Revision as of 23:59, 27 April 2010 by Abillings (talk | contribs) (Created page with '== QA Whiteboard Tags == This is a list of proposed QA-specific tags to be used in the whiteboard for bugs in Bugzilla. The proposal is to have tags that are useful to the QA org…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

QA Whiteboard Tags

This is a list of proposed QA-specific tags to be used in the whiteboard for bugs in Bugzilla. The proposal is to have tags that are useful to the QA organization for the triage, verification, and tracking of bugs, especially around specific releases.

All whiteboard tags for QA begin with qa- and are wrapped in squarebrackets ("[" and "]"). This means that people can always search for "[qa-" in order to find bugs that have had tags added to them.

In addition to the use of tags in the whiteboard, remember that there are the standard "testcase-wanted" and "qawanted" whiteboard items used by the development team. You can also set "?" on the "in-testsuite" flag to ask if it is in a test suite.

Tags

qa-examined-* - This means that QA has "touched" the bug or reviewed it for a particular branch. Branch specific versions should be used as below:

  • [qa-examined-mc] - This bug has been reviewed by QA for trunk (mozilla central)
  • [qa-examined-191] - This bug has been reviewed by QA for Mozilla 1.9.1
  • [qa-examined-192] - etc
  • [qa-examined-193] - etc

Other tags will follow the same pattern in order to be branch specific.

qa-noaction-* - This means that there is nothing for QA to do within this bug. This is branch specific. Use the branch specific versions:

  • [qa-noaction-mc]
  • [qa-noaction-191]
  • [qa-noaction-192]
  • [qa-noaction-193]

[qa-needs-STR] - This is to be used if we need reproduction steps in order to reproduce this bug.