QA/Weave Test Plan/1.3.1

1.3.1 Client Test Plan

This is a one fix release on the client side for a migration bug of logged in users. bug 568136 - Migration requires client to check for a node again after a 401.

1. Run smoketests+ on Primary OS's to ensure 1.3.1 hasn't regressed
2. Run these scenarios around account migration
3. Run same scenarios against live migration setting.

Schedule

• Smoketests/regression checks (mix up platform and Fx branches) (Tracy, Ayan) (prior to 6/7)
  • Results: Pass
    • Win 7
      • Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 - Pass (tracy)
    • Mac
      • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.5pre) Gecko/20100521 Namoroka/3.6.5pre - Pass (tracy)
      • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a5pre) Gecko/20100604 Minefield/3.7a5pre - PASS (ayan)
    • Win XP
      • Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100527 Firefox/3.6.4 - Pass (tracy)

• Smoke the migration process (Telliot, Tracy) (prior to 6/7)
  • Results:
    • Per Telliot email Pass
    • Migrating on stage from node to node Pass (tracy)
• Run Migrations scenarios against stage (Tracy, Ayan) (6/7)
  • Results: Pass
    • After some hiccups on stage configurations we were able to test our Migrations scenarios. All six Pass on accounts using Namoroka nightly builds on Mac 10.6 and 3.6.4 builds on Windows XP (tracy)
    • Ran scenarios 1, 4 and 6 against migration from SJ to PHX with zandr flipping the switch by account. Pass (tracy)
    • Ayan's results - Overall Pass (but meta error still prevails)
      • Tested all scenarios except scenario #2. Got the meta error in Scenario #1 and scenario #6. Tested on build - Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a5pre) Gecko/20100604 Minefield/3.7a5pre - on Mac OS X.Pass(ayan)

• release and test (Tracy, Ayan)
  • Extension release (tracy) (6/8)
    • Results: Pass
  • Migration (tracy) (date tdb)
    • Results: tbd

Comments or bugs found

The meta error noted above is a known issue with configurations of the staging server. It isn't affecting production.