This article provides guidelines for customers on User Acceptance Testing (UAT). It explains the goals and objectives of UAT, highlights typical issues that may arise during UAT, and offers tips for a successful UAT process. The article also discusses bug prioritization and the use of a test management tool called X-Ray. It provides an overview of the UAT phase, including the timeline and week-by-week details. Additionally, it outlines the prerequisites for the UAT phase and emphasizes the importance of training and preparation.

Main topics in this section include:

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.

Seamless Integration: Pricefx UAT Testing for Business Impact".

In our UAT testing phase, our primary goals are straightforward and geared towards ensuring a seamless experience for your business. We aim to comprehensively test the end-to-end process within the real environment, integrating the Pricefx software with your CRM, ERP, and other pricing-related tools. Our focus is on confirming that Pricefx performs as expected, effectively supporting and enhancing your business operations. The ultimate objective is to transition the project into live usage, leveraging the capabilities of Pricefx to positively impact your business.

It's important to note what UAT testing is not: it's not about repeating tests from the Feature Sprints, submitting change requests, or simply getting acquainted with the application. Instead, during this phase, your crucial responsibilities include creating UAT test cases and diligently testing them on the QA partition. If any bugs are identified, we encourage you to report them promptly to JIRA. Your acceptance of the solution is pivotal, marking the formal conclusion of the development phase and signaling the readiness to move forward with the live implementation of the project. We appreciate your collaboration in achieving these milestones and look forward to a successful UAT testing phase.

Efficiently Navigating UAT: Testing, Documentation, and Reporting

During the UAT phase, we've allocated a generous two-week window for testing all your UAT test scenarios. While this timeframe is sufficient, it's essential for testers to be well-prepared and commit daily efforts, dedicating at least 2 to 3 hours each day. We want to emphasize that attempting to tackle the entire testing process in a single day is not the most practical solution, so it's crucial to be ready for a sustained effort over the allocated period. The limited timeframe stresses the need for an organized approach, ensuring that every testing aspect is thoroughly addressed.

In terms of documentation, we've provided test cases for UAT. These serve a dual purpose by not only guiding testers on what needs to be tested during UAT but also offering the flexibility to organize their testing time efficiently and seek clarification on any uncertainties before UAT kicks off. Reporting test results is a key component of this phase. It allows project managers to have a clear overview of the testing progress and what remains to be tested, facilitating effective project management. At the same time, testers gain insights into their completed testing, which is helping them in organizing their ongoing efforts. Additionally, efficient bug reporting in JIRA plays a crucial role in expediting the fixing process.

Common UAT Issues

When UAT testing lacks a structured plan, it often leads to challenges that impact the effectiveness of the testing process. The absence of a defined plan often results in testers resorting to exploratory testing, making it difficult to keep UAT testing under control. Time constraints are a common issue, with insufficient time allocated for comprehensive testing, leaving the progress unmonitored. Problems arise in accepting the solution as UAT testers express a desire to test more, further complicating the process. The absence of prioritization for test cases contributes to critical issues being reported only towards the end of UAT.

Moreover, the absence of training for UAT testers can lead to reported bugs being more akin to questions, change requests, or misunderstandings rather than genuine issues. This lack of clarity can result in UAT testers spending more time learning to navigate the Pricefx application rather than focused testing. The situation is compounded when UAT testers find themselves multitasking, neglecting dedicated time for testing due to other work commitments. To ensure a smoother UAT testing experience, a structured plan, clear priorities, and dedicated time for testing are essential elements that contribute to the overall success of the testing phase. Let's work together to address these challenges and enhance the efficiency of our UAT testing process.

Strategic Approach to UAT Testing

To ensure a streamlined and effective UAT testing process, we recommend a thoughtful, through and organized approach. Begin by selecting a dedicated group of UAT testers, preferably Subject Matter Experts (SMEs), and ensure their commitment and availability for testing. Verify that they have access to all necessary systems required for UAT. The next step involves creating UAT test cases, aligning them with business cases, and ensuring comprehensive coverage of end-to-end scenarios. These test cases should include checklists outlining specific verification points.

Appointing a UAT leader from the project team, someone familiar with the solution, is crucial. UAT testers will report their results to this person, streamlining communication and oversight. Choose a test management tool; we recommend using X-Ray in Pricefx Jira for this purpose, noting that Excel is not considered a suitable test management tool.

Prioritize the training of UAT testers on both the application and the UAT process. Conduct a demo session with all UAT testers, demonstrating how to use the developed software and clarifying expectations for UAT testing. This session, ideally based on UAT test cases, should allow testers to explore the functionality themselves, providing assistance with any initial issues or questions. Recording the session enhances its utility, serving as a valuable reference.

Efficient UAT Testing: Prioritization, Reporting, and Progress Monitoring

UAT testers, equipped with test execution tools such as X-Ray, should prioritize test cases, ensuring that critical functionalities are verified early on in the UAT process. Given the limited time for the UAT phase, it's crucial to keep in mind that there won't be plenty of time for retesting everything covered in Feature Sprints.

Daily reporting of test results is a key practice, with testers logging their progress regularly. The test results should not only include a detailed description of what was tested but also attach screens or other relevant files to provide comprehensive insights. In the event of identifying bugs, testers are encouraged to report them in Jira, categorizing them under Bug and providing a detailed description of the issue, the expected result, and any accompanying screens or files. Post-fix, it's essential to retest all fixes, close the bug, and finalize the testing of the UAT test case.

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 prioritization

Open

Bug prioritization in Jira

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.

Open

Test cases are visible in the Test Board

UAT on the project

UAT summary

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.

Prerequisites 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.

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