QA/Platform/Graphics/Triage: Difference between revisions
No edit summary |
|||
| Line 86: | Line 86: | ||
How to Triage | How to Triage | ||
# [http://mzl.la/ | # [http://mzl.la/1Woj4pa Select a bug from this list] (''it's best sort by most recent changed first'') | ||
# Review the information in the bug and make sure you understand the issue | # Review the information in the bug and make sure you understand the issue | ||
# Request for information from the report if there is information missing (regression window, steps to reproduce, minimized testcase, screenshots, system information, etc) | # Request for information from the report if there is information missing (regression window, steps to reproduce, minimized testcase, screenshots, system information, etc) | ||
Revision as of 18:48, 26 April 2016
Get Involved
The triage sessions detailed below are typically done in private, simply because I'm doing it on my own at this point. If you'd like to get involved, either with me or on your own please, get in touch with me.
- E-mail: ahughes@mozilla.com
- IRC: ashughes in #gfx or #qa on irc.mozilla.org
Schedule
| Category | Next Session |
|---|---|
| Incoming Bugs | Tuesday, April 26, 2016 at 10:00am Pacific |
| Top Crashes | Wednesday, April 27, 2016 at 10:00am Pacific |
| Cold Crashes | Thursday, April 28, 2016 at 10:00am Pacific |
| Cold Tracked Bugs | Friday, April 29, 2016 at 10:00am Pacific |
| Help Wanted Bugs | Monday, May 2, 2016 at 10:00am Pacific |
| Real-time schedule available on ashughes1.github.io | |
Stats
| Date | Help Wanted | Incoming | Top Crashes | Cold Crashes | Cold Trackers |
|---|---|---|---|---|---|
| 2016-04-15 | 25 | 194 | 12 | 387 | 15 |
| 2016-04-22 | 18 | 198 | 14 | 410 | 0 |
| Change from last week | -7 | +4 | +2 | +23 | -15 |
| Change since beginning | -7 | +4 | +2 | +23 | -15 |
| Real-time data available on ashughes1.github.io | |||||
Help Wanted
Once per week, typically on Monday, we review bug reports tagged with help-wanted older than 30 days to ensure these issue are still relevant and on track to resolution.
How to Triage:
- Select a bug from this list
- Review the bug to make sure you understand the bug report and the information needed to move it forward
- Attempt to reproduce the bug
- If you can reproduce the bug, attempt to find a regression window either manually or using mozregression
- Update the bug report with any new information you can provide
- If you can't reproduce the issue or don't understand the issue, move on to the next bug report
Whenever updating a bug report be sure to add a comment explaining the change.
Incoming
Once per week, typically on Tuesday, we review bug reports that were reported more than 30 days ago but have yet to be triaged by the Graphics team.
How to Triage
- Select a bug from this list (it's best sort by most recent changed first)
- Review the information in the bug and make sure you understand the issue
- Request for information from the report if there is information missing (regression window, steps to reproduce, minimized testcase, screenshots, system information, etc)
- If you can reproduce the issue as described then update the bug and escalate it to a graphics developer
- If you cannot reproduce the issue, ask a developer or the reporter if the bug is still valid
- Be sure to add the gfx-noted tag to the whiteboard field once triaged
- Move on to the next bug report if you can
Top Crashes
Once per week, typically on Wednesday, we review our top crash reports to ensure these issues have bug reports on track toward resolution.
- Explosiveness Report: http://bit.ly/1N9iR7j
- Firefox Topcrash Report: http://bit.ly/1VqmLMm
- Fennec Topcrash Report: http://bit.ly/1N9iTfG
- How to Triage
Note: Whenever updating a bug report be sure to add a comment explaining the change.
- Review the reports above
- If you see a graphics crash that doesn't have a bug report, file a bug report for it
- If you see a graphics crash with an associated bug ID, open the bug report and update the statistics for the bug
- If the crash is escalating and is now in top-crash territory, add the topcrash keyword and nominate the bug to track
- If the crash is declining and is no longer in top-crash territory, remove the topcrash keyword
- Repeat the process for each crash you find in the list
Cold Crashes
Once per week, typically on Thursday, we review crash bug reports we have on file that have not been updated in more than 30 days to ensure these issues are still relevant and on track to resolution.
How to Triage:
- Load this list of bugs and sort by most recent changed
- Open the first bug report and review the information
- Check if there are anymore crash reports by clicking the signature link
- If there are no more crash reports, close the bug
- If there are still bug reports, update the statistics in the bug report and see if you can reproduce
- If you can't reproduce, ask the reporter for new information
- If you can reproduce, ask the developer what information is needed to move the bug forward
- Update the bug with any new information and move on to the next bug report
Cold Trackers
One per week, typically on Friday, we review tracked bug reports that have not been updated in more than 30 days to ensure these issues are still relevant and on track to resolution.
How to Triage:
- Select a bug from this list (sort by most recent changed)
- Review the information in the bug report
- Try to deduce if the bug is still relevant through testing, reviewing linked reports, or asking people involved on the bug
- If the bug is still relevant, update the status/tracking flags, and needinfo flag the developer for a status update
- If the bug is no longer relevant, update the status flags and close the bug report
- Once you've updated the bug move on to the next bug report