B2G/QA/Smoke Tests: Difference between revisions

→‎Smoke Tests: added section for Test Automation
(→‎Smoke Tests: added section for Test Automation)
Line 16: Line 16:
** [Browser] Can browse for 1-2 minutes over WiFi
** [Browser] Can browse for 1-2 minutes over WiFi
Note: The telephony tests are done twice to make sure that the process cleans up after itself when the first instance is over so that the second instance is also successful.
Note: The telephony tests are done twice to make sure that the process cleans up after itself when the first instance is over so that the second instance is also successful.
[https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dFlWSDNJdFZjSEM2cU1oWkY2MkFyRHc&usp=drive_web#gid=10 Google Spreadsheet] that tracks daily test logs for Sanity Test Cases.


== Escalation Strategy ==
== Escalation Strategy ==
* When a High Severity Bug is found, it is reported in Bugzilla with the Whiteboard tag "smoketest".
* When a High Severity Bug is found, it is reported in Bugzilla with the Whiteboard tag "smoketest".
* A notification email is sent by QAnalysts to the following mailing lists: mozilla-dev-b2g@lists.mozilla.org, dev-b2g@lists.mozilla.org, dev-gaia@lists.mozilla.org and b2g-release-drivers@mozilla.org
* A notification email is sent by QAnalysts to the following mailing lists: mozilla-dev-b2g@lists.mozilla.org, dev-b2g@lists.mozilla.org, dev-gaia@lists.mozilla.org and b2g-release-drivers@mozilla.org
* The IRC channel owners of #b2g and #gaia are notified in their respective channels.
* The IRC channel owners of #b2g and #gaia are notified in their respective channels.
* A bug is filed requesting OTA to be blocked.
* A bug is filed requesting OTA to be blocked.
Line 53: Line 55:


= Smoke Test Blockers =
= Smoke Test Blockers =
[procedure to follow when Smoke Test Blockers are found]
Bugzilla Query for the Whiteboard tag "smoketest": http://mzl.la/16lkWbM
 
== Escalation Strategy ==
* When a Smoke Test Blocker is found, it is reported in Bugzilla with the Whiteboard tag "smoketest".
* The QA Team is notified in the the #fxosqa IRC channel.
* A regression window for the root cause of the bug is identified.
* The developer who authored the commit is needinfo?ed with a request to back out the commit as soon as possible.
* The Whiteboard tag "[backout-needed]" is added to the bug.
* The [https://wiki.mozilla.org/Modules/FirefoxOS module owner] is also needinfo?ed.
* A Smoke Test report email is sent daily by the Firefox OS QA team to the following mailing lists: fxosqa-report-watchlist@mozilla.org and b2g-release-drivers@mozilla.org
* QA tracks the bug until the commit has been backed out.
* QA requests for a new nightly build to be created.
* When a new build becomes available, QA verifies that the bug no longer reproduces.
 
= Test Automation =
* Gaia UI Tests: https://github.com/mozilla-b2g/gaia/tree/master/tests/python/gaia-ui-tests
Confirmed users
330

edits