Support/Live Chat/SUMO login/Testing

From MozillaWiki
Jump to: navigation, search

Instructions for testing Live Chat account migration


Setup

  1. Before migration starts, make sure to have login credentials for accounts on both servers so that migration of existing accounts can be tested.
    • One account name unique to TikiWiki
    • One account name unique to Openfire
    • Two account names with name conflicts
      • One with TikiWiki account created first
      • One with Openfire account created first
  2. Make sure support-stage.mozilla.org is updated to svn head
  3. Important! Run database query to erase existing livechat_id's created before migration started.
    1. Wait for bug 541983 to be fixed, first
    • UPDATE users_users SET livechat_id=NULL;
  4. Build Openfire from LiveChat trunk to pick up new AuthProvider and openfire.xml changes
  5. IT needs to modify the openfire.xml file to include the database access information for the support-stage database.
    1. Taken care of by bug 541983
  6. Start Openfire, and verify that Openfire accounts are still working properly
    • Server: chat-support-stage.mozilla.com
    • Port: 5222

Testing with a new TikiWiki account

  1. Create a new TikiWiki account on https://support-stage.mozilla.org/tiki-register.php that does not conflict with an existing Openfire or TikiWiki account.
  2. Verify that logging into Openfire works normally with an XMPP client such as Spark.
    • Server: chat-support-stage.mozilla.com
    • Port: 5222

Testing with a new conflicting TikiWiki account

  1. Create a new Openfire account on staging with a unique name.
  2. Create a new TikiWiki account on https://support-stage.mozilla.org/tiki-register.php with the same username from step 1
  3. Log into Openfire and verify that the password first account created, and not the second account created, is used.
  4. Try these steps again with a new username, first creating the TikiWiki account. Openfire should refuse to create a conflicting account in this case.

Testing account migration

After new accounts are confirmed to be working properly, existing accounts must be tested.

Testing existing Openfire account, non-conflicting

  1. Log into Openfire normally with Openfire credentials
  2. If "SUMO login migration" plugin is enabled, the server should ask you to migrate your account after you sign in.
  3. Visit https://support-stage.mozilla.org/tiki-livechat_migration.php as instructed, and follow the steps to create a new TikiWiki account and password. This password should be different than your Openfire password to verify migration
  4. Log out of Openfire, then log back in using your new TikiWiki username and password.


Testing existing Openfire account, conflicting

  1. Log into Openfire normally with Openfire credentials
  2. If "SUMO login migration" plugin is enabled, the server should ask you to migrate your account after you sign in.
  3. Visit https://support-stage.mozilla.org/tiki-livechat_migration.php as instructed, and follow the steps to merge the two conflicting accounts together.
    • Note: the names of the merged accounts don't need to match. After migrating the account, the TikiWiki username/password will be used for both services. To verify this, test migrating different accounts together

Fringe cases to check

(non-inclusive list)

  • Verify that https://support-stage.mozilla.org/tiki-livechat_migration.php refuses to migrate an account if the password is entered wrong.
  • Verify that https://support-stage.mozilla.org/tiki-livechat_migration.php can't be used with Openfire accounts that have been migrated, TikiWiki accounts that have been migrated, or newly created TikiWiki accounts that were created after migration began.
    • Migration changes in all the above cases require an administrator to manually edit the livechat_id
  • Verify that creating a TikiWiki account with invalid JID characters, such as spaces or punctuation, are stripped out after logging into Openfire. (Signing into Openfire will be done with the exact TikiWiki username, including any spaces or punctuation)