Confirmed users
213
edits
B2G/QA/Automation/UI/Minimized Acceptance Execution: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/Automation/UI/Minimized Acceptance Execution (view source)
Revision as of 14:34, 19 March 2015
, 19 March 2015Added flowcharts
(Modified per feedback given) |
(Added flowcharts) |
||
| Line 10: | Line 10: | ||
= Finding a failure in an automation report in an urgent job = | = Finding a failure in an automation report in an urgent job = | ||
== General steps == | |||
* Immediately disable the test per the [[B2G/QA/Automation/UI/Xfail_and_Disable|disable/xfail doc]]. This is the top priority. | * Immediately disable the test per the [[B2G/QA/Automation/UI/Xfail_and_Disable|disable/xfail doc]]. This is the top priority. | ||
* File or update a product bug if it reproduces manually, or an automation bug if it doesn’t, per the [[B2G/QA/Automation/UI/Filing_Bugs_Against_Automation_Errors|bug filing doc]]. | * File or update a product bug if it reproduces manually, or an automation bug if it doesn’t, per the [[B2G/QA/Automation/UI/Filing_Bugs_Against_Automation_Errors|bug filing doc]]. | ||
* Add the failure bug to the next standup highlights, at [https://etherpad.mozilla.org/b2g-automation-daily-standup the standup notes] | * Add the failure bug to the next standup highlights, at [https://etherpad.mozilla.org/b2g-automation-daily-standup the standup notes] | ||
== In details == | |||
[[File:The_test_report_shows_a_test_failure.svg|Detailled flow chart|]] | |||
= Finding a failure in an automation report in a non-urgent job = | = Finding a failure in an automation report in a non-urgent job = | ||
| Line 20: | Line 24: | ||
= Starting work on a bug = | = Starting work on a bug = | ||
* Assign yourself and fill the QA whiteboard to make it appear on the [[B2G/QA/Automation/UI/Scrum|sprint page]] | * Assign yourself and fill the QA whiteboard to make it appear on the [[B2G/QA/Automation/UI/Scrum|sprint page]] | ||
* | * Investigate if it's either an automation issue or an infrastructure one. | ||
* If the issue can be fixed, when your patch is ready, check Treeherder report before going any further. | |||
* If not, nominate it for the flaky suite | |||
* Ask 2 reviewers from either the [[B2G/QA/Automation/UI#Core_Team|core team]] or [[B2G/QA/Automation/UI#Contributors|contributors]]. Only one is needed for enabling/disabling tests. | * Ask 2 reviewers from either the [[B2G/QA/Automation/UI#Core_Team|core team]] or [[B2G/QA/Automation/UI#Contributors|contributors]]. Only one is needed for enabling/disabling tests. | ||
== In details == | |||
[[File:Start_working_on_an_automation_failure.svg|Detailled flow chart|]] | |||
= Finishing work on a bug = | = Finishing work on a bug = | ||