Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

During this phase of the release cycle, Pricefx recommends that customers have an understanding of the state of their current release and overall environment so they can begin the process of designing an upgrade path for the upcoming release.

While you are in the Current Release state of your Pricefx implementation, it is important to start preparations for upgrading to the next major release. In order to be prepared, you will need to answer the following questions:

  • Is my Pricefx solution deployed in a Shared or Private environment?

  • What module capabilities are currently deployed?

  • Will a pending new release contain capabilities advantageous to my deployment?

  • Will pending new release features impact my currently deployed capabilities?

  • What is the QA test plan for the current release? Does it need to be updated for the pending new release?

Managing Upgrades

While planning your release upgrades in your Private Environment, it is important to plan with the following Pricefx constraint in mind since there are some limits on DevOps team for performing these upgrades. Refer to these guidelines:

Upgrade Type

Business Days

Weekends

Major QA upgrades

15-20 per week

NONE

Major PROD upgrades

15-20 per week

Maximum of 3

Minor upgrades

As needed

Automatic for Private ONLY

Upgrade Preparation

When a new release is announced, then the customer should begin their preparations. As a best practice, Pricefx recommends that these steps be performed:

Selection of Testers and Scheduling Upgrade Testing

Selection of a cross-section of skills (business users, administrators, technical, etc) to fully test all aspects of your application against the identified upgrades to the Pricefx core application. Ensure that individuals selected can commit a percentage of their time to this process.

LEARN MORE: To learn more about selecting your release testers and scheduling your upgrade testing, then click here.

Scheduling Upgrade Testing

Ensure that all selected testers have allocated and reserved the appropriate amount of time for performing their specific upgrade testing. The amount of time to allocate to this task will be dependent upon the volume and complexity of their test use cases.

LEARN MORE: To learn more about scheduling your upgrade testing, then click here.

Upgrade System Accessibility

All of your testers will need access to the QA system where the upcoming upgrade has been deployed. Ensure that all access credentials have been defined and all testers are aware of the correct partition to be used for their upgrade testing.

Create Upgrade Test Cases

Prepare the complete set of test cases for your upgrade testing. Each test case should follow a standard format and structure:

-Based on your business cases and should cover all scenarios from beginning to end.

-Based on the current functionality and version of Pricefx before the upgrade.

-Should contain a checklist of what needs to be verified and the expected results.

-Determine the GoLive criteria for the test case.

-Use proper data selection for testing to ensure we have both positive and negative outcomes, and that we are testing for specific scenarios.

LEARN MORE: To learn more about creating your upgrade acceptance tests and to view examples of them, then click here.

  • No labels