Confirmed users
9,511
edits
B2G/UpdateTesting: Difference between revisions
no edit summary
Marshall law (talk | contribs) mNo edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
'''This document is a WIP for the upcoming B2G update test automation in {{bug|821412}}''' | '''This document is a WIP for the upcoming B2G update test automation in {{bug|821412}}''' | ||
== Overview == | |||
When a system update is applied in B2G, it causes either a process restart (OTA) or a device reboot (FOTA), requiring special high level support from a testing framework to automate testing of the various stages of the update. | |||
To solve this problem, specialized Marionette based frontends have been written to solve two different use cases: | |||
# A script based frontend for use by developers, and eventually TBPL | |||
# A "continuous build" smoke testing frontend designed to automatically test updates between builds in a Continuous Integration environment. | |||
== Smoke Tests == | == Smoke Tests == | ||
| Line 32: | Line 39: | ||
==== CI integration ==== | ==== CI integration ==== | ||
* Each CI build should have | * Each CI build should have its update staged for each test device: | ||
<pre> | <pre> | ||
$ testing/marionette/update-smoketests/stage-update.py unagi $B2G_UPDATE_TESTDATA | $ testing/marionette/update-smoketests/stage-update.py unagi $B2G_UPDATE_TESTDATA | ||