QA/Sync/Native Android Test Plan: Difference between revisions

From MozillaWiki
< QA‎ | Sync
Jump to navigation Jump to search
m (Created page with "Outline of Quality Assurance plan to ensure each phase of Native Android Sync is of highest quality possible.[https://wiki.mozilla.org/Services/NativeSync Native Sync team page] ...")
 
Line 5: Line 5:


=== Testing strategy ===
=== Testing strategy ===
QA will getting builds very late in the game.  We will keep up with phased releases of this feature as follows:
QA will keep up with phased releases of this feature as follows:


* Milestone 1 (Jan, 16, 2012)
* Milestone 1 (Jan, 16, 2012)

Revision as of 21:54, 6 January 2012

Outline of Quality Assurance plan to ensure each phase of Native Android Sync is of highest quality possible.Native Sync team page and [].

Client

Native Android Sync is a stand alone apk that will be bundled with Fennec. As such many of its features are tied to the android system. It doesn't need Fennec to be running to be syncing.

Testing strategy

QA will keep up with phased releases of this feature as follows:

  • Milestone 1 (Jan, 16, 2012)
    • Ensure full Account Setup and J-PAKE slave are supported
    • Ensure sync across multiple devices for History and Bookmarks
    • L10n support (landed Dec 20th, but we won't be able to test until localizers do their thing)
  • Milestone 2 (Jan 31)
    • Ensure Milestone 1 features have not regressed
    • Ensure Backoff and error handling are fully supported
    • Ensure Passwords and Tabs sync across multiple devices
  • Milestone 3 (Target with first native Fennec release March 30, 2012)
    • Ensure M1 and M2 features have not regressed
    • Verify any polish stability fixes.
    • If ready, ensure BrowserID+Sync is supported.

Schedule

  • Milestone 1
    • Builds to QA by Jan 12, 2012
    • Sign-off by Jan. 14, 2012
  • Milestone 2
    • Builds to QA by Jan. 27, 2012
    • Sing-off by Jan. 39, 2012
  • Milestone 3
    • ??

notes

  • If I understood this correctly, Instant Sync is not supported because the system decides when to sync.
  • This should work with most any android device. Though initially there will be issues with UI on tablets.