canmove, Confirmed users
2,041
edits
QA/B2G WebAPI Test Plan: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
= | =Boot2Gecko WebAPI Test Plan= | ||
== Summary == | == Summary == | ||
{| class="fullwidth-table" | {| class="fullwidth-table" | ||
| Line 15: | Line 16: | ||
| [[WebAPI]] | | [[WebAPI]] | ||
|} | |} | ||
== Scope == | |||
This test plan covers qualification of WebAPIs developed for or used specifically in Boot2Gecko to interface with mobile devices. It does not cover the entirety of Gecko APIs available. The individual APIs covered are listed below and broken out into their own individual test plans. | |||
== Strategy == | |||
Test strategy will vary between APIs based largely on how dependent they are on actual device hardware. B2G continuous integration will offer two options: [https://developer.mozilla.org/en/Mochitest mochitest-plain] and a new [[Auto-tools/Projects/Marionette|Marionette]]-based JS harness. | |||
Tests written against the new harness will run only in B2G CI against QEMU, a device emulator. They can set things like orientation or battery status to a known value, which allows for rich virtual device manipulation for fixture setup. | |||
Tests written against mochitest-plain can run in the standard mozilla-central [https://tbpl.mozilla.org/ Tinderbox] test environment and anywhere else mochitests are typically run, as well as against the B2G codebase. Mochitest will give wider coverage, but will not be able to use the emulator to set up device-related fixtures and are thus significantly more limited. | |||