QA/Weave Test Plan/FirefoxHome/1.1 testplan
From MozillaWiki
< QA | Weave Test Plan | FirefoxHome
Summary of Changes
The list of bugs fixed in all the builds below are presently listed on Stefan's status page.
Builds
- build 1.1b2
- Tryserver build with v0.9 patch
- build 1.1b4
- build 1.1b5
Schedule
- 1.1 eta Early Dec
Test Plan
General
- Run standard smoketests
- Verify other bugs that were fixed in this version. (See notes)
- Test against latest iOS3.1.x and iOS4.x
Allow passphrases on storage version 4 (bug 617153)
- 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)
Bookmark Changes (bug 615639)
- Given storage bump, verify bookmarks are unchanged:
- sync order
- name, titles
- remove, add a bookmark, resync
Simplified Crypto ((bug 605734)
- 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)
Easy Setup using J-PAKE (bug 593130)
- Q: Are there known issues if adding across platforms? nope
- Test jpake screen sign in
- Log out, log in, verify error messages
- Verify timeout on j-pake login screen is 5 minutes, before throwing error
- Test fallback sign in
- Verify refreshing gives a new jpake code
- Log out, log in, verify error messages
Upgrading (bug 616312)
- 1.0.4 and Fx3.6.12+1.5 or Fx3.5.15+1.5 or Fx4b7 (no updates)
- no errors
- upgrading to 1.1 also shows no errors
- 1.1 and Fx3.6.12+1.5 or Fx3.5.15+1.5 or Fx4b7 (then update to sync 1.6)
- 1.1 cannot update to crypto. error thrown saying: "data in server is in the newer format." (won't sync, but can access existing data)
- option to re-sign in. this way user isnt forced to wipe and start over.
- 1.0.4 and Fx4b8 or FF beta7+1.6 or Fx3.6.12+1.6 or Fx3.5.15+1.6
- error thrown when sync on 1.0.4 happens: "data is new in an recognized format. please update ff home."
- once updated to 1.1, they will be presented with jpake
- Users will have to re login and sync once updated to 1.1
Localization Strings (bug 615647)
- Verify j-pake setup screen changes
- Verify fallback setup screen changes
- Verify error messages
- incorrect sign in
- incompatible version screen
- Upgrade needed screen
- jpake network timeout
Test Results for 1.1b5
- Tester: tchung
- Build ID: tbd
- Result: not yet
- Notes