...
Test management - details
...
In case the customer is more experienced and he is more interested in how UAT phase will be performed on the project, you can use the second version of the slide deck:
...
UAT on the project
UAT overview
The UAT testing phase is geared towards achieving several key objectives. Firstly, it aims to rigorously test the end-to-end process in a real environment, combining Pricefx software with your CRM, ERP, and other pricing-related tools. This includes thorough assessments of both functionality and integration aspects during UAT. The overarching goal is to ensure that Pricefx software seamlessly supports and enhances your business operations. The ultimate outcome is to transition the project into live usage, allowing it to actively contribute to your business needs.
It's crucial to note that UAT testing is distinct from repeating tests from Feature Sprints, submitting change requests, or simply getting familiarized with the application. As a customer, your responsibilities include creating UAT test cases covering the end-to-end process, testing according to these cases on the QA partition, reporting any identified bugs through JIRA or other agreed-upon bug reporting tools, and finally, accepting the solution to formally conclude the development phase. Your active engagement and commitment to these UAT goals are instrumental in the project's success.
Timing is paramount for the success of the UAT phase. The pre-UAT phase, spanning two weeks between Feature Sprints and UAT, is dedicated to finalizing preparations. The UAT phase itself, lasting between 2 to 6 weeks, depends on the project's length and complexity. This duration allows for comprehensive testing of all UAT end-to-end test cases, including functionality checks and retesting of fixes on the QA partition. However, it's essential to emphasize that even within this timeframe, effective preparation is key. Test cases must be well-prepared, and testers should be clear on expectations, dedicating at least 2 to 3 hours daily for regular testing. An organized approach is imperative due to the limited timeframe.
Expected UAT documentation includes comprehensive test cases, aiding testers in understanding testing requirements and allowing them to manage their time efficiently. Reporting of test results, including clear bug descriptions and useful attachments in JIRA or other agreed-upon bug reporting tools, ensures an expedited fixing process.
Prerequisities for UAT phase
Before entering the UAT phase, a collaborative effort between our customer and the Pricefx team is essential. For the customer, this involves completing testing within Feature Sprints and accepting all user stories in scope. Ensuring the QA partition contains accurate data for UAT is equally crucial. Additionally, creating UAT test cases for end-to-end testing, selecting dedicated UAT testers with allocated time, and appointing a UAT test leader to oversee test result reporting are key tasks.
Meanwhile, on the Pricefx side, our commitment is to finalize the development of user stories within the specified scope.
Timeline of UAT phase
...
UAT details – week by week
Training and preparation
As we gear up for the UAT phase, both the customer and the Pricefx team have pivotal tasks in training and preparation. For the customer, finalizing UAT test cases is a key step, coupled with guiding UAT testers on expectations. A dedicated demo on the QA partition helps testers familiarize themselves with the test cases they will be handling. Allowing UAT testers to initiate their first round of testing and offering support for any queries or issues is integral. Additionally, the customer is tasked with selecting a test management tool and leader for the UAT testing phase, ensuring seamless access to tools, environments, and login credentials.
Meanwhile, on the Pricefx side, our commitment is to wrap up bug fixing from the last Feature Sprint, aligning efforts for a smooth UAT experience.
System Integration testing
In the lead-up to the System Integration testing phase, just as before, both Pricefx and the customer have key roles. For the customer, ensuring the seamless functioning of all integrations on the QA partition is a priority. This involves allowing UAT testers to initiate their first round of testing, providing necessary guidance to ensure their comfort with expectations. The week is dedicated to ensuring UAT testers have the final version of end-to-end test cases and are well-prepared for testing. Additionally, any integration issues identified are diligently logged into JIRA or another agreed-upon bug reporting tool.
On the Pricefx side, we commit is to swiftly address and deploy fixes for any integration issues identified during this testing phase.
End to end testing – 1st week
Beginning the crucial first week of End-to-End testing, collaboration between teams becomes central focus. For the customer, the central tasks focus on initiating testing based on the carefully prepared E2E test cases. Prioritizing top-level and lengthy test cases ensures a strategic testing approach. The proactive logging of bugs daily in JIRA or an agreed-upon bug reporting tool, coupled with daily progress reporting to the UAT test leader, creates a robust feedback loop.
Retesting of fixed bugs forms an integral part of this process, contributing to the iterative improvement of the solution. Simultaneously, on the Pricefx side, the commitment is to address and fix bugs, with a clear understanding that deployments should be avoided during the sensitive UAT testing period.
End to end testing – following weeks
As we enter the subsequent weeks of End-to-End testing, the collaboration remains essential. The customer will focus on diligently continuing testing based on the comprehensive E2E test cases. The goal is to finalize all test cases within the week, ensuring a thorough and efficient testing process. Daily bug logging in JIRA, coupled with regular progress reports to the UAT test leader, maintains a robust feedback loop. At the same time, the Pricefx team is committed to promptly addressing and fixing bugs, with a clear understanding that deployments should be deferred during the sensitive UAT testing period.
Bug fixing and retesting
In the next phase, the customer plays a key role in ensuring the successful conclusion of UAT testing. Tasks include meticulously preparing the scope for the final regression testing, emphasizing the retesting of reported bugs to verify fixes. Additionally, selected UAT test cases are retested on the QA partition to ensure the correct functionality of the application. Daily bug logging in JIRA or another tracking tool is encouraged as a precautionary measure, although the expectation is to encounter no new issues during this crucial week. Frequent progress reports to the UAT test leader ensure transparent communication. The culmination involves final regression testing after bug retesting, leading to the crucial Code Freeze. Final acceptance concludes the UAT phase. Simultaneously, on the Pricefx side, bug fixing and deploying all changes to the QA partition are prioritized, with the last UAT week designated as a Code Freeze, unless a critical issue arises.