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.

Automation | Article
OpenAI’s Data agent could investigate company data and build shareable interactive dashboards. Access controls and source trails needed to follow analysis and action through the workflow.

Project management | Event
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.

Automation | Article
Power BI reports and semantic models became grounding in Copilot Chat and Cowork. Shared chats, synced notebooks and Planner status connected analysis with collaboration.

Project management | Article
Copilot Notebooks and Cowork gained more ways to share project context. Agent metrics and cost controls expanded in the admin centre.

Automation | Article
Copilot administrators gained central controls for consumption-based cost. Purview controls extended to Cowork, and agent metrics could connect with organisational context.

Project management | Article
Federated connectors could retrieve live SaaS data through MCP. Copilot Notebooks gathered project context while Word and Teams gained collaboration features.
Do you have a question or experience to share?
Be the first to contribute.