B2G/QA/Automation/UI/Minimized Acceptance Execution: Difference between revisions

B2G/QA/Automation/UI/Minimized Acceptance Execution (view source)

593 bytes removed , 18 March 2015

Moved the new template part to B2G/QA/Automation/UI/Filing_Automation_Report

Confirmed users

213

edits

@@ Line 24: / Line 24: @@
 = Transition plan =
 In order to get to the escalated jobs suite, here's how we'll proceed to reduce the daily human intervention:
-# Reduction of the length of the automation report (see the new template)
+# Reduction of the length of the automation report (see the [[B2G/QA/Automation/UI/Filing_Automation_Report|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 ==
-    Subject: 02/18/2014 Acceptance tests results - Smoketests passed - Non-smoketests 1 new failure, 3 remaining.
-    Smoketests: Passed. No product failure to call out. Automation failures: *insert a mzl.la link to a bugzilla request*
-    Non-smoketests: One new product failure.
-        * Bug 1134035 - [Dialer] Tapping the top call log entry, selects and deselects the 2nd call entry in edit mode
-remaining failures: *insert a mzl.la link to a bugzilla request*
-    Build under test: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-kk/2015/02/2015-02-17-16-02-34/