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.
Upgrade test coverage
|Upgrade system||Types of testing to conduct||What to resolve in this stage|
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.
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.
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.
|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|
|Remedy Asset Management||ITSM_ProductUseCases-Validation-AM.pdf|
|Remedy Change Management||ITSM_ProductUseCases-Validation-CM.pdf|
|Remedy IT Service Management Suite Foundation||ITSM_ProductUseCases-Validation-FND.pdf|
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.