B2G/QA/Weekly Bug Review: Difference between revisions
| (13 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
* QA & Smoketest Blockers | * QA & Smoketest Blockers | ||
* QA Requests | * QA Requests | ||
* | * Firefox OS QA Bugs Filed Last Week | ||
* QAnalyst-Triage Bugs | * QAnalyst-Triage Bugs | ||
| Line 29: | Line 29: | ||
== Non-Blocking & Non-Nominated Regressions == | == Non-Blocking & Non-Nominated Regressions == | ||
'''Goal: ''' Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted) and/or be nominated to block the first applicable release. Add those keywords respectively to any bugs you think could benefit from QA help. Nominate any bug respectively that you should be blocking with a rationale included on the bug. | '''Goal: ''' Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted) and/or be nominated to block the first applicable release. Add those keywords respectively to any bugs you think could benefit from QA help. Nominate any bug respectively that you think should be blocking with a rationale included on the bug. | ||
* [http://mzl.la/1uUgrvu Non-Blocking Regressions] | * [http://mzl.la/1uUgrvu Non-Blocking Regressions] | ||
| Line 38: | Line 38: | ||
'''Goal: ''' Analyze each of the below queries to determine if any bugs have stagnating progress towards resolution. Notify the release QA lead of any bugs determined to be stagnating. | '''Goal: ''' Analyze each of the below queries to determine if any bugs have stagnating progress towards resolution. Notify the release QA lead of any bugs determined to be stagnating. | ||
* QA Blockers | * [http://mzl.la/XEKFaU QA Blockers] | ||
* Smoketest Blockers | * [http://mzl.la/1o3XJhc Smoketest Blockers] | ||
== QA Requests == | == QA Requests == | ||
== | '''Goal: ''' Analyze each of the below queries to determine if any bugs no longer need QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted). Remove those keywords respectively to any bugs you think could no longer need QA help with a rationale why. | ||
* [http://mzl.la/1DkZsIK Blocking ?/+ QA Requests] | |||
* [http://mzl.la/1mbQNmL Blocking -/backlog QA Requests] | |||
* [http://mzl.la/1qZpwnk Non-Nominated QA Requests] | |||
== Firefox OS QA Bugs Filed Last Week == | |||
'''Goal: ''' Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted) and/or be nominated to block the first applicable release. Add those keywords respectively to any bugs you think could benefit from QA help. Nominate any bug respectively that you think should be blocking with a rationale included on the bug. | |||
* [http://mzl.la/1mfDq4w Firefox OS QA Bugs Filed Last Week] | |||
== QAnalyst-Triage Bugs == | == QAnalyst-Triage Bugs == | ||
'''Goal: ''' Analyze each of the below queries to determine if any bugs got stuck in the QAnalyst-Triage workflow due to forgetting a part of the workflow (e.g. didn't needinfo the lead, didn't put the right QAnalyst-Triage flag, didn't respond to a QAnalyst-Triage- bug). Notify the tester involved in the workflow to fix the problem identified via a needinfo request. | |||
* [http://mzl.la/1uUrbKw QAnalyst Bugs Last Week - No QAnalyst-Triage] | |||
* [http://mzl.la/1BNvNWS QAnalyst Bugs with QAnalyst-Triage-] | |||
* [http://mzl.la/1wEIuTR QAnalyst Bugs with QAnalyst-Triage?] | |||
Latest revision as of 21:45, 17 September 2014
Overview
On a weekly basis, we need to look at certain bug queries to assess different areas. The types of queries to analyze are below.
- Feature QA Bugs
- Release Blockers
- Non-Blocking & Non-Nominated Regressions
- QA & Smoketest Blockers
- QA Requests
- Firefox OS QA Bugs Filed Last Week
- QAnalyst-Triage Bugs
Feature QA Bugs
Goal: Analyze each of the below queries to determine if any bugs have stagnating test coverage and verifications respectively. Notify the release QA lead of any bugs determined to be stagnating.
Note: These queries will need to be updated each release, since the queries above represent test coverage and verifications of the current active release only.
Release Blockers
Goal: Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted). Add those keywords respectively to any bugs you think could benefit from QA help.
Non-Blocking & Non-Nominated Regressions
Goal: Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted) and/or be nominated to block the first applicable release. Add those keywords respectively to any bugs you think could benefit from QA help. Nominate any bug respectively that you think should be blocking with a rationale included on the bug.
QA & Smoketest Blockers
Goal: Analyze each of the below queries to determine if any bugs have stagnating progress towards resolution. Notify the release QA lead of any bugs determined to be stagnating.
QA Requests
Goal: Analyze each of the below queries to determine if any bugs no longer need QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted). Remove those keywords respectively to any bugs you think could no longer need QA help with a rationale why.
Firefox OS QA Bugs Filed Last Week
Goal: Analyze each query below to determine if any bugs could benefit from QA request help (e.g. qawanted, steps-wanted, regressionwindow-wanted) and/or be nominated to block the first applicable release. Add those keywords respectively to any bugs you think could benefit from QA help. Nominate any bug respectively that you think should be blocking with a rationale included on the bug.
QAnalyst-Triage Bugs
Goal: Analyze each of the below queries to determine if any bugs got stuck in the QAnalyst-Triage workflow due to forgetting a part of the workflow (e.g. didn't needinfo the lead, didn't put the right QAnalyst-Triage flag, didn't respond to a QAnalyst-Triage- bug). Notify the tester involved in the workflow to fix the problem identified via a needinfo request.