Confirmed users
486
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:33, 9 March 2015
, 9 March 2015→Transition plan
(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 | # Reduction of the length 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. | # 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. | # Stop to send out the manually written automation report. Product bugs will be covered in the general daily report. | ||