QA/Weave Test Plan/FirefoxHome/1.1 testplan

From MozillaWiki
Jump to navigation Jump to search

Summary of Changes

TODO

  • Next build:
    • bug 615639 Implement bookmarks change
    • bug 615647 Include string changes for v1.1

CHANGES

  • New and Improved in 1.1b5:
    • bug 615724 GET /report should be POST /report
    • bug 615898 Localized labels are clipped on EasySetupViewController
    • bug 612358 Create artwork for the new JPAKE screen
    • bug 615955 Localized labels are clipped on WelcomePage
    • bug 615972 Start using the production JPAKE server
    • bug 615660 Localized labels are clipped on ManualSetupViewController
    • bug 616073 Sporadic crash when cancelling the EasySetupViewController
    • bug 616021 JPAKE error dialog pops up at random intervals
  • New and improved in 1.1b4:==
    • bug 615623 Include Thai translation
    • bug 615625 Include Indonesian translation
    • bug 615484 FF Home: J-pake screen is not localized
    • bug 615428 FF Home: Crashing on iOS3 when launching fallback screen
    • bug 615631 Crash on GMail URL
    • bug 615632 Added sync feedback to the search screen
    • bug 615633 Custom server is never forgotten
  • New and improved in 1.1b3:
    • bug 605734 Implement easy setup in Firefox Home based on J-PAKE (FIXED)
    • bug 605724 Adopt simplified crypto in FxHome (FIXED)
    • bug 611898 Home should check syncID and storage Version changes and act accordingly (FIXED)
    • bug 608460 Change the User Agent of Firefox Home to include the OS version (FIXED)
  • New and improved in 1.1b2:
    • bug 605734 Implement easy setup in Firefox Home based on J-PAKE (IN PROGRESS)
    • bug 605724 Adopt simplified crypto in FxHome (FIXED)
    • bug 611898 Home should check syncID and storage Version changes and act accordingly (IN PROGRESS)
    • bug 608460 Change the User Agent of Firefox Home to include the OS version (FIXED)
  • New and improved in 1.1b1:
    • bug 605734 Implement easy setup in Firefox Home based on J-PAKE

Builds

Schedule

  • 1.1 eta Early Dec

Test Plan

  • Run standard smoketests
  • Verify other bugs that were fixed in this version. (See notes)
  • Test against latest iOS3.1.x and iOS4.x
Testcases
  • Test for allowing 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)
  • Test for Bookmark Changes (bug 615639)
    • Given storage bump, verify bookmarks are unchanged:
      • sync order
      • name, titles
      • remove, add a bookmark, resync
  • Test for Upgrading
  • 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
  • Test for 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)
  • Test for Jpake (bug 593130)
    • Note: need a dev try server build with latest sync installed to test
    • 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
  • Test for Strings (bug 615647)
    • Need screens for all string changes in the UI

Test Results for 1.1b3

  • Tester: tchung
  • Build ID: tbd
  • Result: not yet
  • Notes
    • Filed bug 615428 - FF Home: Crashing on iOS3 when launching fallback screen
    • Filed bug 615484 - FF Home: J-pake screen is not localized