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:56, 5 March 2015
, 5 March 2015Minor indentation fix
(Added Geo's first feedback.) |
(Minor indentation fix) |
||
| Line 30: | Line 30: | ||
= Transition plan = | = Transition plan = | ||
In order to get to the escalated jobs suite, here's how we'll proceed to reduce the daily human intervention: | In order to get to the escalated jobs suite, here's how we'll proceed to reduce the daily human intervention: | ||
# Reduction of the lenth of the automation report (see the new template) | |||
# Configure Jenkins to send out email on every single failures (use [https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin this plugin] to configure the content of the email. | |||
# Stop to send out the manually written automation report. Product bugs will be covered in the general daily report. | |||
# Split the jobs between flaky/non-flakies. | |||
== New report template == | == New report template == | ||