Acceptance testing is often the final quality check before a delivery is approved, where end users test the system against the customer's requirements. Use this approach in the final phase of a delivery, or earlier in the project to identify risks along the way.
Review the requirements specification, user stories, and acceptance criteria with the customer before testing begins.
List all types of end users relevant to the acceptance testing of the deliverable.
Decide whether acceptance testing should be carried out as a final quality check before completion, or earlier in the project to identify risks along the way.
Based on the requirements, create test scenarios in Azure DevOps Test Plans for each user type.
Describe the scenarios in the user interface, preferably illustrated with screenshots, so that the testers know exactly what to do.
Have the test lead review the test scenarios before testing begins to ensure that they actually cover the requirements and acceptance criteria for each user type.
Create individual test cases based on the scenarios and run them with the relevant end users.
Approve each test case that has been completed without deviations from the requirements.
Create a bug for each failed test case, and send it on for fixing and retesting.
Ask a question or share what helped you.
Published 1/27/2026
ProsessPilotene is among the first companies in Norway to be included on the Microsoft FastTrack Portfolio Partners List—a mark of quality awarded to providers that deliver complex Dynamics 365 projects in accordance with documented best practices.
Read more
Published 9/29/2025
Jets Group was looking to modernize its business systems and planned to start with ERP. Along the way, it became clear that the foundation for growth lay not in the technology, but in understanding and improving customer processes.
Read moreDo you have a question or experience to share?
Be the first to contribute.