...
Is our environment N-1 compliant?
If not compliant, we will be compliant before the end of the Grace Period?
Do I have a plan for maintaining my N-1 Compliance?
What is the probability of an automatic upgrade?
What is the status of my release testing?
Release Pending Phase Tasks
During this phase the upgrade acceptance testing should have already begun, and should consider the impact of the following:
Upgrade Testing Process
Confirm that testing in QA has/is being performed to assess how the upgrade will impact the environment 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 the 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 aren not discovered and resolved before the upgrade, the production application will be temporarily unavailable until resolved.
Upgrade Test Plan Progress
Confirm the status and progress of the upgrade testing and test plan. It is a good time to review the test plan timeline and its completion as compared to N-1 compliance timeline and communicate this information to Pricefx. If completion of the acceptance testing is not anticipated prior to the expiration of the release Grace Period, then contact Pricefx.
| Info |
|---|
LEARN MORE: To learn more about the development of a Test Plan, guidelines, and recommendations for this task, click here. |
Acceptance Testing Progress
Confirm with the team of selected testers that they have been performing the necessary test cases assigned to them. Confirm they have had the proper time allocation to fulfill the upgrade test plan in its entirety and to determine if there are undiscovered gaps in the upgrade preparation.