QA/Weave Test Plan/1.3/Migration

Account Migration Testing

Scenarios provided below are for testing of and around bug 568136 - Migration requires client to check for a node again after a 401.

Testing Scenarios

1. Account Migration
   1. Create accounts with 1.3.0 on Server A (in this case, set a custom server of https://stage-auth.services.mozilla.com/)
   2. Ensure those accounts are properly syncing between at least 2 different clients.
   3. Upgrade all clients to Sync to 1.3.1
   4. Ensure clients still sync properly
   5. Run account migration to Server B (For initial testing, this will migrate from one node to another on stage)
   6. Again ensure the accounts are properly syncing between at least 2 different clients. (note node change in the sync logs)
2. Sync during migration
   • Notes: There could be race conditions here. The migration script will account for changes in timestamps. But there is a tiny hole for LDAP replication. That could cause problems. It's very unlikely we'll be able to trigger that one.
   1. Follow the Account Migration scenario, except, attempt to sync clients while the account migration is taking place in step 5.
   2. Depending on timing, the account may or may not show as being migrated.
   3. If the account shows as not migrated, another sync later should show migrated account.
3. Upgrade of existing accounts at PHX
   1. Create accounts with 1.3.0 with default server (all new accounts should go to phx)
   2. Ensure those accounts are properly syncing between at least 2 different clients.
   3. Upgrade all clients to Sync to 1.3.1
   4. Ensure those accounts continue to properly sync between at least 2 different clients.
4. 1.3.0 clients logged in during account migration
   1. Create accounts with 1.3.0 on Server A (in this case, set a custom server of https://stage-auth.services.mozilla.com/)
   2. run migration script Server A
   3. Attempt sync with 1.3.0 accounts. (Accounts will 401)
   4. Disconnect and reconnect, then sync.
   5. Verify sync changed server nodes
5. 1.3.0 clients logged out during account migration
   1. Create accounts with 1.3.0 on Server A (in this case, set a custom server of https://stage-auth.services.mozilla.com/)
   2. Disconnect clients
   3. run migration script Server A
   4. Reconnect and attempt sync with 1.3.0 accounts.
   5. Verify sync changed server nodes
6. Add a client after Migration
   1. Create an account with 1.3.1 on Server A (in this case, set a custom server of https://stage-auth.services.mozilla.com/)
   2. Run account migration to Server B (For initial testing, this will migrate from one node to another on stage)
   3. Add a second client to sync with this account
   4. Ensure both clients are properly syncing (note node change in the sync logs)