canmove, Confirmed users
2,041
edits
B2G/QA/WebAPI Test Plan/On Device: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/WebAPI Test Plan/On Device (view source)
Revision as of 23:48, 14 August 2012
, 14 August 2012→Strategy
| Line 16: | Line 16: | ||
== Strategy == | == Strategy == | ||
APIs can be accessed from | 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. | ||
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. | 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. | ||