...
Main topics in this section include:
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The following information about UAT is useful especially for first communication about UAT or when the customer has low experience with UAT and needs our support.
...
We recommend checking the testing status every day to ensure a steady pace and efficient progress. The UAT Leader should actively monitor the progress of UAT testers, providing necessary support and guidance.
...
Bug
...
UAT Finalization
The finalization of UAT testing signifies our readiness to transition into the Go-Live phase and utilize the solution in production. It's important to note that medium and low-priority bugs should not impede acceptance, as they can be addressed post Go-Live during the Stabilization phase. The decision to accept or not should align with the specified timeframe for the UAT phase, with a clear decision at the end.
The key steps for a QA transitioning to go live include:
Completing testing within Feature Sprints and accepting all user stories in scope
Ensuring the QA partition contains accurate data for UAT
Creating UAT test cases for end-to-end testing and selecting dedicated UAT testers
Appointing a UAT test leader to oversee test result reporting
Finalizing the development of user stories within the specified scope
Ensuring seamless functioning of all integrations on the QA partition
Prioritizing top-level and lengthy test cases for strategic testing
Daily reporting of test results and bug logging in JIRA or other agreed-upon bug reporting tools
Retesting of fixed bugs and final regression testing after bug retesting
Decision to accept or not aligning with the specified timeframe for the UAT phase
...
prioritization
...
Test management
...
with X-Ray
...
X-Ray, is a Pricefx tool for test management plug-in integrated into JIRA. It comes with no additional cost to the project. This tool enhances transparency by making test documentation and results visible to both our project team and customers. Test cases are organized in separate issue types, linked to user stories for clarity on their purpose. It seamlessly supports testing in both Feature Sprints and UAT, ensuring an easy-to-use experience for anyone familiar with JIRA. With functionalities like exports, imports, and workflows, X-Ray has been successfully utilized on Pricefx projects since April 2021 and extended for customer UAT since October 2021.
...
...
UAT on the project
UAT summary
...
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.
Go-Live Transition
UAT Finalization
The finalization of UAT testing signifies our readiness to transition into the Go-Live phase and utilize the solution in production. It's important to note that medium and low-priority bugs should not impede acceptance, as they can be addressed post Go-Live during the Stabilization phase. The decision to accept or not should align with the specified timeframe for the UAT phase, with a clear decision at the end.
The key steps for a QA transitioning to go live include:
Completing testing within Feature Sprints and accepting all user stories in scope
Ensuring the QA partition contains accurate data for UAT
Creating UAT test cases for end-to-end testing and selecting dedicated UAT testers
Appointing a UAT test leader to oversee test result reporting
Finalizing the development of user stories within the specified scope
Ensuring seamless functioning of all integrations on the QA partition
Prioritizing top-level and lengthy test cases for strategic testing
Daily reporting of test results and bug logging in JIRA or other agreed-upon bug reporting tools
Retesting of fixed bugs and final regression testing after bug retesting
Decision to accept or not aligning with the specified timeframe for the UAT phase