In this section you will learn about how to deal with Upgrade testing upgrades during the project are requested.

Upgrade testing overview

There are 10 main steps you need to be aware of when testing fro upgrades. Keep these in mind at all times as they will help you in making the best possible calls and assessments throughout the process.

1. Select testers and schedule Upgrade testing 

2. Make sure all testers have time for Upgrade testing every day 

3. Ensure all testers have access to all tested systems and inbound integrations are working correctly on QA partition 

4. Create test cases based on E2E business cases and prioritize them based on use case importance 

5. Select data for testing, make sure you select data for positive, negative and specific cases 

6. Make sure test cases contain expected results and and go-live criteria 

7. Test according to prepared test cases, start from the highest priority and positive scenarios 

8. Log bugs to Jira and retest after they are fixed 

9. Promote core code from QA to Prod only when testing is complete 

10. Conduct smoke testing in Prod prior to general release 

Typical issues during Upgrade testing

No Upgrade testing at all

In case of any issues or misunderstandings that may surface later, rest assured they will be promptly addressed under the COSA framework.

There might be a temporary interruption in the functionality of the Pricefx software after deployment to production, rendering its use temporarily unavailable leading to missing benefits during this period.

Missing plan for Upgrade testing

Testers are engaging in exploratory testing without prior preparation, resulting in disorganized upgrade testing. The lack of clarity on priorities for test cases further hampers efficiency, as the most crucial cases are not being addressed promptly or primarily.

Testers lack time for testing

This situation is a very common ocurence. Testers are not testing because they are doing other work. The fact that this happens more that we would like does not change the fact that it can lead to delayed upgrade testing or no upgrade testing at all. Therefore it is recommended that testers only focus on testing at this time to ensure a seamless process.

Tips - Before Upgrade testing

Select a group of testers

As we prepare for the upgrade testing phase, our approach involves selecting a dedicated group of testers who are familiar with the Pricefx software before the upgrade. Ensuring their availability and access to necessary systems is paramount.

Create test cases for upgrade testing

The creation of comprehensive test cases, based on current business cases and covering end-to-end scenarios, is a key focus. These test cases are tailored to reflect how the Pricefx software is currently utilized before the upgrade, including checklists for thorough verification. Prioritizing data selection for testing, covering positive, negative, and specific scenarios, is another critical aspect.

Choose the test leader and the test management tool

Appointing a dedicated test leader to collect results and inform managers is essential, along with choosing an appropriate test management tool, potentially utilizing X-Ray in Pricefx Jira or Excel for smaller test cases.

Tips - During Upgrade testing

During the Upgrade testing phase, testers equipped with Test execution, especially if X-Ray is used, prioritize test cases, focusing on critical functionalities at the beginning for a strategic testing sequence. Daily logging of test results, including attached screens and detailed descriptions, forms a comprehensive feedback loop. Reporting bugs in Jira under the designated Bug category is encouraged, with clear descriptions, expected results, and relevant files provided for efficient issue resolution.

Retesting all fixes, promptly closing bugs, and concluding testing for the respective test cases are integral steps. Daily progress checks, led by the Test Leader, further contribute to transparency and efficiency. This synchronized testing approach ensures a thorough evaluation during the Upgrade testing phase, enhancing the overall quality of our software.

Bug prioritization