B2G/QA/Identity: Difference between revisions
Jump to navigation
Jump to search
(→Scope) |
|||
| Line 44: | Line 44: | ||
=== Infrastructure === | === Infrastructure === | ||
* Use http://notoriousb2g.personatest.org/test for running QUnit automation on device | |||
* Host test sites (e.g. people.mozilla.com) with DOM id code to test the UI directly | |||
* Reuse existing top sites that use persona to regression test for no obvious bustage | |||
=== Automation === | === Automation === | ||
Revision as of 06:40, 12 December 2012
Identity
Overview
This document will cover how testing of the identity pieces should be done on the Firefox OS platform with trusted UI.
Division of Responsibility
| Test Area | Lead |
| B2G Integration Testing | Jason Smith (irc: jsmith) |
| Identity UI Regression Testing | John Morrison (irc: jrgm) |
| Identity Server-Side Testing | John Morrison (irc: jrgm) |
B2G Integration Testing
Overview
The goal of this test area is to analyze the b2g-specific implications to the identity implementation - including the DOM ID pieces and the trusted UI.
Scope
- Functional smoke and basic functional testing to ensure that trusted UI + DOM ID integration into B2G specifically works as expected
- Reusing existing QUnit automation to ensure that the existing tests still pass with the b2g-specific implementation
Signoff Criteria
Pref on Feature
- [MISSED] Smoke tests for feature should pass
- [DONE] QUnit Automation Suite should be green
- [DONE] Feature complete on client-side implementation
- [MISSED] No smoketest blockers
- [MISSED] Peer signoff by John
Infrastructure
- Use http://notoriousb2g.personatest.org/test for running QUnit automation on device
- Host test sites (e.g. people.mozilla.com) with DOM id code to test the UI directly
- Reuse existing top sites that use persona to regression test for no obvious bustage