Confirmed users
4,072
edits
Litmus:How to Triage Failed and Unclear test cases: Difference between revisions
Litmus:How to Triage Failed and Unclear test cases (view source)
Revision as of 16:47, 5 November 2008
, 5 November 2008no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 9: | Line 9: | ||
* A "[litmus] Daily Report - <date>" email sent each morning for reports from the previous day | * A "[litmus] Daily Report - <date>" email sent each morning for reports from the previous day | ||
* A link at the bottom of most litmus pages can be found for [https://litmus.mozilla.org/search_results.cgi?order_by_created=DESC×pan=all&result_status=fail&limit=50 recent failures] and [https://litmus.mozilla.org/search_results.cgi?order_by_created=DESC×pan=all&result_status=unclear&limit=50 recently unclear] results. | * A link at the bottom of most litmus pages can be found for [https://litmus.mozilla.org/search_results.cgi?order_by_created=DESC×pan=all&result_status=fail&limit=50 recent failures] and [https://litmus.mozilla.org/search_results.cgi?order_by_created=DESC×pan=all&result_status=unclear&limit=50 recently unclear] results. | ||
* A ''Stats Page - to be created'' is available to link to various Litmus queries for tracking triage progress | * A ''Stats Page - to be created'' is available to link to various Litmus queries for tracking triage progress. This page links to vetted and unvetted lists. Unvetted results are the ones that need to be reviewed. | ||
= Review Failed results daily = | = Review Failed results daily = | ||
| Line 19: | Line 19: | ||
* If the day of triage shows just a few valid reports, the lead can usually take on bug filing. However, if there are a lot of valid failed results, the Litmus lead should forward the results to the appropriate subgroup owner for them to take action. In which case, it will be their responsibility to file the bug then Vet the result. | * If the day of triage shows just a few valid reports, the lead can usually take on bug filing. However, if there are a lot of valid failed results, the Litmus lead should forward the results to the appropriate subgroup owner for them to take action. In which case, it will be their responsibility to file the bug then Vet the result. | ||
* Vet the result. Vetting is a way to mark results as having been reviewed and action taken. Once you are done with result validation and action taken, click the '''Vet Result''' button in the result report. | * Vet the result. Vetting is a way to mark results as having been reviewed and action taken. Once you are done with result validation and action taken, click the '''Vet Result''' button in the result report. | ||
* Add a bug reference to the report under referenced bugs. Enter the bug number, then click ''Add Bug References''' | |||
* Add a comment as to the action taken, then click '''Submit Comment''' | * Add a comment as to the action taken, then click '''Submit Comment''' | ||
| Line 30: | Line 31: | ||
* Vet the result. Vetting is a way to mark results as having been reviewed and action taken. Once you are done with result validation and action taken, click the '''Vet Result''' button in the result report. | * Vet the result. Vetting is a way to mark results as having been reviewed and action taken. Once you are done with result validation and action taken, click the '''Vet Result''' button in the result report. | ||
* Add a comment as to the action taken, then click '''Submit Comment''' | * Add a comment as to the action taken, then click '''Submit Comment''' | ||
= Result of this process = | |||
* More bugs filed on broken features | |||
* Clearer test case suites. | |||