B2G/QA/Triage

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

The use of QA contact field should be set optimally when the person is actively investigating something in relation to the bug, usually in connection to one of the keywords above. The QA contact field should aim to only be set by the person who is planning on working on the bug for some piece of QA.

There are some exception cases to this rule however stated below.

The first case is if an explicit owner is known up front for a component who actively manages the bugs. In this case, the default QA contact will be used to address QA needs for the bugs.

The second case is if a high need is raised in triage to find an owner for a bug. In this case, triagers should set the QA contact to the QA representative in triage to find a QA owner to address QA needs for the bug. If no QA representative is present, then one of the two sheriffs should be set as the QA owner by area:

• Gaia General: Naoki Hirata
• Platform General: Geo Mealer
• Apps Gaia and Platform: Jason Smith

Priorities

For addressing bugs that need QA involvement with the keywords stated above, the table below summarizes the three priorities we follow along with a target SLA.

Priority	Bugzilla Flags	Initial Response SLA	Query
High	blocking-b2g = ?, tef+, shira+, leo+	3 days	Bug Query
Medium	blocking-b2g = -	As time and resources allow with no P1s available	Bug Query
Low	Anything else	As time and resources allow with no P1s and P2s available	Bug Query