User Acceptance Testing (UAT)
In this stage, stakeholders and end users company-wide test the release processes and give their feedback. This stage is crucial for any product release as users test and validate the release using a large volume of real-time data. It takes a holistic approach to the release by bringing deep insights on the design, execution, customer expectation, user experience, and more.
UAT involves the following:
- Mapping out a detailed plan for the UAT.
- Outlining business requirements and strategy.
- Identifying and creating test cases that cover as many user-functional cases as possible.
- Selecting users to take a trial of the release processes and provide feedback. You can offer the release package to the intended users as a beta-trial or early adoption.
Users perform initial functionality tests on the release processes. After the processes succeed the functionality tests, users then test them using valid data in the production environment and determine whether they meet the proposed business requirements.
All issues found during the UAT must be carefully documented to follow up for the resolution. Potential bugs and high-priority functionality issues are immediately fixed. Other issues are added to the pipeline of the next iteration.
The UAT team approves the release after ensuring that the processes function as expected and move it to the deployment.
To add and view UAT-related details,
- Go to Releases.
- Choose all or a specific customer from the drop-down in the header.
- Go to the details page of the required release.
- Click UAT on the left pane.
On the canvas, the following tabs are displayed:
- Details:
- spot edit the relevant fields to provide the expected and actual UAT time frame.
- Describe the UAT process under Description.
- Attach test plan files.
- Attach records of the issues found while testing.
- Tasks: Add, edit, organize, delete, pick up, trigger, and close release tasks, assign owners to the unassigned tasks, and configure task dependencies. Learn more.
- Notes: Provide UAT-related additional information. You can also add UAT notes via conversations.
- Approvals: Define approvers for various approval levels required to complete the UAT. Learn more.
- Status Comments: View all UAT status comments provided in the release form.
Related Articles
UAT
User Acceptance Testing (UAT) is the stage in which some users evaluate the implemented change under real-world scenarios. Based on their experience during the testing period, the UAT members provide their consent on approving the change. Role ...Testing
In this stage, the processes built for the release are tested for common bugs and functionality issues by the Quality Assurance (QA) team. This is done to check whether the development has met the requirements outlined in the release plan without ...Stage and Status
The progress of each stage in a release life cycle is tracked by specific statuses. You can create and manage stages and statuses for the release under Setup > Customization > Release Management > Stage and Status. Users with Edit Releases permission ...User Groups
Classify users in your help desk instance into various groups based on certain criteria. You can allow/restrict users to access certain items in the instance via user groups. To configure user groups, go to Setup > Users and Permissions > User ...User Survey
ServiceDesk Plus MSP Cloud allows you to create and send surveys to customers and collect their valuable feedback and responses. To access user survey, go to Setup > User Survey. You can configure surveys in two ways: ServiceDesk Plus MSP Cloud ...