Confirmed users
14,525
edits
QA/Desktop Firefox/Walkthroughs/Automation: Difference between revisions
Jump to navigation
Jump to search
QA/Desktop Firefox/Walkthroughs/Automation (view source)
Revision as of 20:35, 15 April 2014
, 15 April 2014→Instructions for QA Leads
| Line 18: | Line 18: | ||
</pre> | </pre> | ||
2. | 2. Be sure to include links to the various automation reports ([[Releases/Firefox_31/Test_Plan#Automation|live example]]) | ||
3. Periodically review the list for ''fixed'' bugs and check the dashboards to verify the failure has been resolved | 3. Periodically review the list for ''affected'' bugs to make sure investigation stays on track, comment in the bug if you require a status update | ||
4. Periodically review the list for ''fixed'' bugs and check the dashboards to verify the failure has been resolved | |||
* Mark the bug REOPENED if the test continues to fail | * Mark the bug REOPENED if the test continues to fail | ||
* Mark the bug VERIFIED FIXED if the test has not failed recently | * Mark the bug VERIFIED FIXED if the test has not failed recently | ||
5. Ask for the test to be disabled if the test consistently fails on Beta/Release | |||
6. If the Automation Development determines a failure is related to a Firefox regression: | |||
* Add the ''qawanted'' keyword to the regression bug | * Add the ''qawanted'' keyword to the regression bug | ||
* Assign a QA Contact to take ownership of the testing (Florin Mezei if you are unsure) | * Assign a QA Contact to take ownership of the testing (Florin Mezei if you are unsure) | ||