...
Are my acceptance tests successful?
If any acceptance test is failing, how am I logging these errors?
Are acceptance errors in the Pricefx Core or are they within my solution’s Configuration?
Who is responsible for correcting any acceptance errors?
Have all of my acceptance test cases been identified and created?
Release Available Phase Tasks
Before starting the upgrade acceptance testing, the impact of the following should be considered:
...
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.
Upgrade Preparation During Release
During the Release period of the upgrade cycle, and as a best practice, Pricefx recommends that these steps to be performed:
...
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:
Priority | Explanation |
|---|---|
CRITICAL | User is unable to use the solution, resulting in a critical impact on business operations. This condition requires immediate resolution. (i.e. The system is down) |
HIGH | Any high priority defect which results in an incorrect price calculation. No workaround is available, and the defect is time sensitive. (i.e. Defect is blocking pricing from being exported to ERP systems) |
MEDIUM | The defect requires attention but does not block pricing utilization. A workaround is available but may not be optimal. (i.e. Defect requires the user to perform manual calculations) |
LOW | Minor loss of functionality. These may be monitoring issues, clarifications, documentation questions, or administrative tasks. (i.e. Update the column label or any other cosmetic related defects) |
Each of the testers should be logging their results every day. If an issue is discovered, then the appropriate level of documentation to assist in fixing the issue should be provided (i.e. expected vs. actual result, error messages, screenshots, etc).
...