Hi Everyone,
Our B2G QA team has put together a short wiki that summarizes how we
will triage incoming requests for QA support here -
https://wiki.mozilla.org/B2G/QA/Triage. This document aims to clarify
what keywords to use in what situation, how the QA contact field is
used, and our different triage queries we use by urgency for addressing
QA requests. Some areas from this documentation that's worth noting
includes the following:
* For QA requests, aim to use one of the keywords specified in the
wiki that best represents the request being made. Need STR on a bug?
Use steps-wanted. Need a regression window? Use
regressionwindow-wanted. Need specialized QA support that doesn't
fit any QA keyword? Use qawanted.
* The QA contact field should optimally aim to be set by the QA
intending to be working on the bug. Two exceptions on this rule
include:
o When there is a known default owner on the bugs (e.g. I test
calendar bugs), a default QA contact is defined and used by
default for QA requests
o When there is a high need to find an owner on a bug during
blocking triage, the QA representative in triage should be set
as the QA contact to find an owner to look at the bug. If there
is no representative in triage, then the QA contact field should
be set to either Naoki (Gaia), Geo (Platform), or myself (Apps)
based on the specific area the bug falls into.
* We address QA requests by order of three buckets - bugs that are
blocking? or blocking+, bugs that are blocking-, and any other bug.
If you have any questions, comments, feedback on this process, please
feel free to let our team know.
--
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
