...
Upgrading QA Cluster (+ all associated partitions)
Perform intensive QA Cluster testing across complete functionality
Evaluate the results of upgrade acceptance testing, resolve any issues
Upgrade PROD Cluster
Perform intensive PROD Cluster testing across complete functionality
Identify issues and notify Pricefx Support as needed
| Info |
|---|
NOTE: Learn more about use of Partition Copy in Pricefx, and how it is commonly used for go-live preparations, QA purposes, training, and demo purposes. Click here. |
Why should I upgrade?
Our product is constantly evolving as improvements and advancements in our core product are applied in support of our customer's and industry’s needs. We are constantly listening to our customers to fully understand their pricing environment, learn about their issues, and identify the opportunities they provide for further innovation. Within the product team, these new features are reviewed for impact on customer value, developed along key value drivers, beta tested, revised, and improved, and then finally become part of a major release.
...
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. (ie. 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. (ie. 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. (ie,. Defect requires the user to perform manual calculations) |
LOW | Minor loss of functionality. These may be monitoring issues, clarifications, documentation questions; or administrative tasks. (ie. Update the column label or any other cosmetic related defects) |
Each of our 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 (ie. expected vs actual result, error messages, screenshots, etc).
...