Confirmed users
2,177
edits
TestEngineering/Performance/Triage Process: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Triage Process (view source)
Revision as of 12:07, 10 June 2020
, 10 June 2020no edit summary
m (add triage center link) |
No edit summary |
||
| Line 2: | Line 2: | ||
=== Triage Duty === | === Triage Duty === | ||
Your main goal during triage duty is to make sure bugs are labelled appropriately and quickly based on recent bug activity. This might mean checking bug activity once a day, perhaps doing some minimal investigation, and then updating the bug's priority, severity, product, status, need-info, etc. | Your main goal during triage duty is to make sure bugs are labelled appropriately and quickly based on recent bug activity. This might mean checking bug activity once a day, perhaps doing some minimal investigation, and then updating the bug's priority, severity, product, status, need-info, etc. | ||
| Line 22: | Line 21: | ||
* If it is not clear how to proceed on the bug, or if further input is necessary from stakeholders, add the whiteboard entry '''[perftest:triage]'''. Those bugs will be discussed in the next [https://docs.google.com/document/d/1SeMijarFsdtm-mrxkIQzV4y1PHcJN72JDPWOlxJ7u-A/edit#heading=h.v37yirv4o0rn triage meeting]. | * If it is not clear how to proceed on the bug, or if further input is necessary from stakeholders, add the whiteboard entry '''[perftest:triage]'''. Those bugs will be discussed in the next [https://docs.google.com/document/d/1SeMijarFsdtm-mrxkIQzV4y1PHcJN72JDPWOlxJ7u-A/edit#heading=h.v37yirv4o0rn triage meeting]. | ||
=== Review Queue === | |||
To ensure that we're responding to review requests in a timely manner, the [https://phabricator.services.mozilla.com/tag/perftest-reviewers/ #perftest-reviewers] group is triaged once/day. This involves tracking the number of open review requests and assigning a team member to be responsible for the review. | |||
* Open the '''Reviews''' sheet in [https://docs.google.com/spreadsheets/d/1R_hqmzvvnOu_0iBvuEAgx-KhxPXZ6xXqGEkrMrmDo6s/edit#gid=579213543 this spreadsheet]. | |||
* Click the green '''+''' button to create a new row with today's date. | |||
* Open the [https://phabricator.services.mozilla.com/dashboard/view/84/ FxPerfTest dashboard] in Phabricator. | |||
* Note total number of reviews in the '''perftest''' tab and enter this into the sheet under the '''Total''' column. | |||
* Count the number of reviews that have a last update of more than 24 hours and enter this into the sheet under the '''>24hrs''' column. | |||
* Count the number of reviews that have a last update of more than 48 hours and enter this into the sheet under the '''>48hrs''' column. | |||
* Check that the '''<24hrs''' column is automatically populated based on the values entered. | |||
* Check that the '''Review Queue''' chart reflects the new values. | |||
* For any review that '''only''' have the '''#perftest-reviewers''' as the reviewer, assign a team member as a blocking reviewer. | |||
** The reviewer should be the next team member in rotation to balance the load across the team, however this may not be disirable if many large reviews are building up on an individual. Use the team member tabs to understand the review queue for individuals and your best judgement. | |||
=== Queries === | === Queries === | ||