QA/Weave Test Plan/FirefoxHome/1.1 testplan: Difference between revisions

** Allow three types of sync key to be entered to login to the sync account:

*** 26 digit sync key : base32decoded (with our own alphabet)

*** 26 digit hyphenated sync key : base32decoded (with our own alphabet)

*** passphrase : PBKDF2(passphrase, syncID)

** Given storage bump, verify bookmarks are unchanged:

*** sync order

*** name, titles

*** remove, add a bookmark, resync

**Test for backward compatibility  

*** Sync with an existing account  

*** Sync with a new account created in beta 8

**Test from old crypto to new crypto  

***check old sync keys (custom key, generated key, and jpake keys)  

*** Change your Sync key and update, and retry syncing on Device.  Should see an error on device saying "incorrect Sync Key" and direct back to setup screen.

**** Test sign in again via Jpake

**** test sign in again via Fallback setup (new password)

*** Change your password and update, and retry syncing on Device.  Should see an error on device saying "incorrect Sync Key" and direct back to setup screen.

**** Test sign in again via Jpake

**** test sign in again via Fallback setup (new sync key)

**'''Q: Are there known issues if adding across platforms?'''  nope  

**Test new account sign up

**Test existing account sign up

**When adding a device, enter in correct j-pake key

**Enter in incorrect j-pake key

**'''Q: Whats the timeout when jpake server isnt returning?''' 5 mins

**Test fallback logon screen

**Logging in and out, and re-adding device