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

QA/Weave Test Plan/FirefoxHome/1.1 testplan (view source)

Revision as of 21:48, 6 December 2010

320 bytes added , 6 December 2010

m

→‎Test Plan

Tchung

Confirmed users

6,361

edits

@@ Line 58: / Line 58: @@
 *Test for Upgrading
-** Upgrading from 1.0.4 when using Sync 1.5: Since Home 1.1 is backward compatible, these two scenarios should simply work as they do in 1.0.4. User should not notice anything.
+*1.0.4 and Fx3.6.12+1.5 or Fx3.5.15+1.5 or Fx4b7 (no updates)
-*** From 1.0.4 with username as account
+** no errors
-*** From 1.0.4 with email address as account
+** upgrading to 1.1 also shows no errors
-** Upgrading from 1.0.4 when using Sync 1.6:  In this case when the user has used 1.6, the data has been changed to use new crypto. Home should notice at next sync and tell you to sign in again. It should also give you a cancel option so that you are not forced to sign in (and lose your data).
+* 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
+bookmarks
+- test bookmark order remains the same as what desktop is syncing
+- storage bumped change, but we need to verify bookmarks are still sync'ed and no data loss happens
 *Test for Crypto