QA/Desktop Firefox/Triaged Bug List: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 20: Line 20:
** if a bug is hard to understand, too complex
** if a bug is hard to understand, too complex
** Canned Response:
** Canned Response:
*** qa?:  
*** qa?: more information needed
* qa!: QA has done all it can to test this bug
* qa!: QA has done all it can to test this bug
** verified across all affected branches and platforms
** verified across all affected branches and platforms

Revision as of 22:32, 26 September 2011

QA+ Triage Strategy for Bug Verifications

In the Whiteboard field in the bug we'll use [qa+], [qa-], [qa?] and [qa!] according to the following criteria:

  • qa+: QA needs to verify the fix
    • nightly: VERIFIED FIXED status
    • aurora: verified-aurora keyword
    • beta: verified-beta keyword
    • the test case to verify the fix should be clearly defined
    • Canned Response:
      • qa+: tracking to verify fix (indicate branches needed for verification)
  • qa-: QA can/will/need not verify the fix
    • build config bugs
    • code-cleanup bugs
    • unsupported platforms (ie. OS/2, Solaris, PPC Mac, etc)
    • bugs with the assertion keyword
    • Canned Response:
      • qa-: nothing for QA to verify
  • qa?: More information is needed for QA to decide on qa+/-
    • if a bug is missing a testcase or steps to reproduce
    • if a bug is hard to understand, too complex
    • Canned Response:
      • qa?: more information needed
  • qa!: QA has done all it can to test this bug
    • verified across all affected branches and platforms
    • made a reasonable effort reaching out to domain experts or bug reporters who, in the absence of clear steps to reproduce or test cases, can verify the bug

We will be triaging bugs on a regular, weekly basis, from a list pulled from hg to include a week or two weeks worth of checkins.

Bug Query Mechanics

Go to the pushlog page and query for the last 2 weeks worth of bugs depending on how recently you have had a triage session. Then apply the "collect buglinks" bookmarklet to get a list of bugs from the pushlog, and go through those.

  • Jesse's Bookmarklets Page
    • Visit this link and right-click on the fourth bookmarklet item from the top. Add this to your Bookmarks Toolbar.

Go through this list which should contain a list of recently Fixed bugs and apply the criteria above to triage them.

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Desktop_Firefox/Triaged_Bug_List&oldid=351559"