Performing upgrade testing

Follow the guidance in this topic to understand what you should test and resolve in each of the upgrade environments: development, QA, and production.

 

In this topic

Upgrade test coverage

Upgrade system

Types of testing to conduct

What to resolve in this stage

Development

Test the upgrade process.

Test the functionality of the system with focus on ensuring that your application customizations are working with the enhancements or changes that have been introduced in this version of the applications.

QA

Test upgrading with a copy of your production data, and test importing the customizations and fix packages that you will import to production for your final upgrade.

  • Perform out-of-the-box functionality testing.
  • Perform end-to-end user acceptance testing to validate data and to check that customized applications and integrations are working correctly.
  • Conduct performance testing to confirm system performs as expected under load.
  • (Optional for a staged upgrade) Test the delta data migration process.

Best practice
We recommend that you conduct full validation and performance testing in the QA environment to minimize the amount of time required for testing during the production upgrade.

  • As you conduct User Acceptance Testing (UAT), resolve issues related to application customizations and overlays. Return to the development system to fix those application customizations and to create another packing list with the corrections. On the QA system, re-import the customizations and re-test.

  • Resolve issues with OOTB product functionality. Check the Support Knowledge Base and the Release-notes-and-notices of the specific component for known issues and workarounds. If needed, contact Support for fixes. Apply fixes to the development environment and create a fix package that you will import to production.

    Note: For a staged upgrade, create separate fix packages for data (.arx) fixes and non-data fixes. You will apply non-data fixes and apply data fixes in separate steps.

  • Resolve issues with performance. Review tuning parameters and tune the system as recommended. Verify that your environment meets the minimum Hardware-requirements for the data load.

 Production

Perform sanity tests to ensure systems and applications are functioning and to verify data integrity.

User Acceptance Test (UAT) cases for applications

The attached files contain sample scenarios for UAT.

Application

Sample test matrix

BMC Asset Management

BMC Change Management

BMC Remedy IT Service Management Suite Foundation

Incident Management

Problem Management

Release Management

Performance testing and tuning

For information on how to conduct performance testing, see Performance-benchmarking-guidelines-for-the-Remedy-platform-and-applications.

For tuning recommendations, see Performance-tuning-for-Remedy.

Related topics

List-of-objects-modified-in-19-08

Where to go from here

Up to process

If you have finished testing, return to the appropriate task in the upgrade process:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*