/
Upgrade UAT Recommendations

Upgrade UAT Recommendations

Overview

This page provides general recommendations for testing your LearningBuilder UAT instance.

Ahead of your upgrade, we will provide you with a Risk Assessment: a customized document to help you understand which customizations in your LearningBuilder system may be affected by the upgrade. This will help you formulate a test plan for your system. Alternatively, you can choose to contract with Heuristics to create an assisted test plan for you.

Please keep in mind that the Heuristics QA team thoroughly tests all “First-Class” features for every release, so you can be confident that the majority of your system has already been tested. Customizations such as integrations and stored procedures are not tested internally.

Principles of Testing

All testing for your upgrade should take place in your UAT environment, which will be upgraded several weeks ahead of your production environment.

As you explore the system, you may encounter any number of issues that raise questions. We are eager to hear your observations and will do our best to address your questions. As you approach testing, there are a few principles to follow:

  • If you observe something that looks different, it may not represent a defect in the upgrade. Please make note of your observation and let us know, but do not immediately come to the conclusion that the system is “broken.” It is possible that the behavior or display you see may be an intentional choice.

  • If you observe something that looks different, do not automatically assume that the change was intentional. LearningBuilder is a complicated system and while we do our best to understand all the implications of an upgrade, we are human. Reporting a difference to us, even if it seems harmless, may help us uncover a deeper problem in the system. Your feedback can make a huge difference to us and to the rest of the LearningBuilder community.

  • If you see something that doesn’t look right in the UAT environment, please check it against your Production environment before reporting the issue as related to the upgrade. We find that many of our customers, upon examining their configuration, find existing gaps or adjustments they would like to make but are unrelated to the upgrade itself. We urge you to log these items but differentiate them from upgrade-specific issues. To minimize the complexity of the upgrade process, we will request that we postpone any configuration changes until after the upgrade is complete.

Common Testing Recommendations

Every LearningBuilder site contains different configuration and customizations. We always recommend you test the following items (if applicable) in UAT prior to signing off on a production upgrade:

  • Enter at least one copy of all applications through submission and approval

  • Review public directory results

  • Run copies of all commonly used reports

  • Print Queue (if applicable)

  • Data Import or Attendance Upload

  • Integrations (Please note: Not all integrations can be accurately tested due to limitations with third party environments.)

Information to Include When Reporting an Issue

If you identify an issue while testing your upgrade, please respond to your Jira Upgrade ticket via email. This will bring the issue to the attention of our Upgrade Coordinator, who can ensure it is resolved in time for your upgrade.

In order to assist you in determining the cause of an issue, please include the following information:

  • Confirm the environment in which you see the issue.

  • Confirm that you have checked against the Production environment and notice a difference between the two.

  • Provide a description of the Role you were using (for instance, “I was logged in as an Applicant).

  • Provide the member details, when available (for instance, “I was accessing Juan Alexander’s record, e-mail address xxx@xx.com, ID: 85956).

  • Include the area or page within the system where you observed the issue (for instance, “I was on the Eligibility Queue” or “I was viewing the person’s Member Details page”).

  •  Include the specific workflow(s) you were using (for instance, “I loaded the Continuing Education Activity”).

  • Describe your observations.

  • Include a screen capture if the observation can be illustrated visually, and try not to crop out important details such as the Learning Plan name or the applicant’s name.