B2G WebAPI On-Device Test Plan

Summary

Scope

This is a description of the WebAPI testing to be performed on devices running Boot2Gecko/Firefox OS. This plan does not cover Gaia testing, or any other end-to-end experience testing. It only covers tests designed to verify WebAPIs but which require interactive testing to do so.

Strategy

APIs can be accessed from JavaScript code running in one of four contexts: content, webapp, privileged webapp, and certified webapp. Of the four, content and certified webapps are the most interesting for functional testing.

Content is interesting because it can be tested quickly via the browser rather than loading in a separate app. This makes content-based testing particularly attractive for dogfooders, because it can occur on any build anywhere.

Certified WebApps are interesting because they have access to all APIs without running into permission restrictions; in fact, many APIs can only be accessed by certified WebApps. However, certified apps need to be part of the core Gaia delivery, which requires inserting a test app into local builds at build time.

The on-device test strategy will take advantage of both these contexts, with an abbreviated matrix designed for on-browser testing, and a longer matrix designed for testing within a certified WebApp. Where possible, these methods will share code.

Areas will be added to the matrix opportunistically as the code for them is written or existing exercises are located.

Test Schedule

TBD

Matrixes

Note: these are untriaged. Some of these APIs may not be testable in a way that makes sense, and may be removed from the matrix entirely.

Content (Browser)

Certified WebApp

This page is based on the WebAPI Test Plan Template