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:04, 18 March 2015

163 bytes removed ,  18 March 2015
Moved the triage part to B2G/QA/Automation/UI/Triage
(Moved the triage part to B2G/QA/Automation/UI/Triage)
Line 21: Line 21:
== Flaky trend analysis ==  
== Flaky trend analysis ==  
Every triage, the team is in charge to take a look at the trends of failures. If a test got worse from the last triages, a bug to investigate the potential reasons of the failures will be filed. If a test went above 50% *TODO: does this value look correct?* a failures, a bug will be filed to remove it.
Every triage, the team is in charge to take a look at the trends of failures. If a test got worse from the last triages, a bug to investigate the potential reasons of the failures will be filed. If a test went above 50% *TODO: does this value look correct?* a failures, a bug will be filed to remove it.
= Triages =
On bugzilla, QA Whiteboard: [fxosqa-auto-suite-triage?]
Event: Every week, either during the automation roundtable or another event of half an hour


= Transition plan =
= Transition plan =
Jlorenzo
Confirmed users
213

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1062723"

Navigation menu