...
Before starting the upgrade acceptance testing, the impact of the following should be considered:
Upgrade Testing Process
Testing in QA is the customer’s opportunity to assess how the upgrade will impact their Production from both a change and risk perspective. For example, to reveal if changes or updates would be needed to SSO or ERP integrations, or help bring superusers up to speed on the new release.
If no upgrade testing is performed, then all issues, misunderstandings, or problems encountered later are resolved under COSA. If these issues are not discovered and resolved before the upgrade, then the production application will be temporarily unavailable until resolved.
Upgrade Test Plan
Existence or creation of an organized and disciplined approach to upgrade testing, is important in avoiding any undiscovered gaps in the test plan that could lead to potential problems. A common symptom is when testers are performing tests without proper preparation and prioritization of critical functionality. There should always be a clear prioritization of specific test cases.
| Info |
|---|
LEARN MORE: To learn more about the development of a Test Plan, guidelines, and recommendations for this task, click here. |
Time Allocation
Ensure that the team of selected testers has the necessary time to perform the test cases assigned to them due to the volume of their other work. Without the proper time allocation to fulfill the upgrade test plan in its entirety undiscovered gaps in the upgrade preparation will inevitably appear.
...
During the Release period of the upgrade cycle, and as a best practice, Pricefx recommends that these steps to be performed:
Logging Bugs
As the upgrade testing progresses and various issues are discovered, these errors need to be logged so fixes can be applied and then re-tested. Any errors discovered should be prioritized using the following suggested set of categories:
...
| Info |
|---|
LEARN MORE: To learn more about the practice of logging and cataloging any errors that are encountered, click here. |
Code Promotion
Once all of the test cases have been performed and the results have been verified, it is time to promote the core code from the QA system to the PROD environment.
Upgrade Smoke Test
The final step of the checklist will be the performance of a smoke test or build verification test to determine if all of the most critical functions of the application are performing as expected. This is a preliminary test of the new upgrade and its functionality.
| Info |
|---|
LEARN MORE: To learn more about resolutions to common issues related to Pricefx upgrades, click here. |