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

From MozillaWiki
Jump to navigation Jump to search
m (→‎Triage Meetings: Removed outdated meeting info)
Line 46: Line 46:


== Triage Meetings ==
== Triage Meetings ==
<pre>
 
  When: Wednesdays at 9am PDT
  Where: Zombocom
Dial-in: 650-903-0800 or 650-215-1282 x92 Conf# 262 (US/INTL)
        1-800-707-2533 (pin 369) Conf# 262 (Toll Free)
    IRC: irc.mozilla.org #qa for backchannel 
</pre>


; Past Meetings
; Past Meetings
* [[QA/Desktop_Firefox/Triaged_Bug_List/Meetings/2011-10-26|October 26, 2011]]
* [[QA/Desktop_Firefox/Triaged_Bug_List/Meetings/2011-10-26|October 26, 2011]]

Revision as of 18:05, 8 September 2014

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?: 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?: We need more information to verify this bug.
  • 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!: 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
  • qa^: QA would like higher prioritization on this bug from dev:
    • qa has seen this bug and triaged but the bug has not been dev prioritized
    • QA has seen this bug and dev priority and qa priority does not match due to end user usability issues.
    • This is mostly used for the mobile team, as dev prioritizes the bugs with dev priority using the priority field.

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.

Triage Meetings

Past Meetings