External Testing

« Return to Notes Listing

Author:Aaron
Last Updated:May 20, 2022 3:37 PM

Provide Client User Acceptance Testing (UAT) Information

Testing is important! If user do not sign off on the upgrade, it is not guarenteed to go smoothely. Ensure that users are testing in the correct environments: Instances on v6.9.5 will have External Testing in dev. The Production (host-prod-2) instance already exists. Instances on v6.9 or lower will test in new prod (host-prod-2). Make sure you confirm with Brian that the client has access to the environment they are testing in. When testing in new prod (host-prod-2) ensure that DomainConfig has been updated to disallow and IIS bindings have been added in IIS.

  1. The Test Plan used in the Dev Instance QA step, should be simplified and provided to clients for testing.
    1. If the Test Plan included a Product Catalog, send the client a specific list of links to test (they do not need to test all)
    2. If Search is important, send them links to the search page and ask them to search for specific terms and confirm results
    3. If there are any customizations, send the user instructions for testing the customization.
  2. It's important to manage the feedback from the clients. This is the first time, in potentially years, that clients have looked at their instances to test them. It is not uncommon for users to report an existing bug or feature request as something "broken" in an upgrade. If the bug exists in the old version, it should be handled as support after the upgrade. If it is a feature request, it should be proposed as new work. Some issues will just be training.

CLIENT UAT SIGN-OFF (PRE-LAUNCH)

  1. Each item in the Testing Plan should be tested. A team member should sign off that each item is working as exptected.
  2. The following testing steps should be followed:
    1. If a bug is found, a ticket should be created as a subtask of the upgrade project. 
    2. A resource should be assigned to fix the issue (BED or FED)
    3. When the resource has fixed the issue, it should be sync to the repo if it is a code change and reassigned to the AD for verification. 
  3. When all issues have been closed and the External Team agrees, External Testing is complete.
  4. Production upgrade cannot be scheduled until this step is completed.

Schedule Production Upgrade

  1. Schedule final upgrade with client – Upgrade must be scheduled between 8am – 5pm on Mondays – Wednesdays.
  2. Upgrades are not scheduled on Thursdays or Fridays to avoid unknown issues that requires weekend or after hours support. If a client requires it, this can be scheduled, but there must be an agreement for additional support.
  3. Client should be aware of the content freeze during the upgrade and that they can change DNS is needed.
top