> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/testing/acceptance-testing.md).

# Acceptance Testing

Acceptance testing is the final stage of the development process where a product is checked to ensure it meets all the requirements and is ready for real users. In this phase, the focus shifts away from finding small technical bugs and toward verifying that the software actually does what it was designed to do. It acts as a formal review where stakeholders or end users test the system in a realistic environment to confirm it solves the specific problems it was built to address.

There are generally two main types of this method known as alpha and beta testing. Alpha testing is usually done by internal staff who look for any remaining issues before the product leaves the building. Beta testing follows this by giving a nearly finished version to a small group of actual customers. Their feedback provides an honest look at how the product performs in the wild, helping the team catch any overlooked frustrations before the official launch.

Ultimately, the goal of acceptance testing is to provide confidence to the business and the developers. Passing these tests signifies that the product is "good enough" to be released and that it delivers the expected value. By involving the people who will actually use or pay for the tool, the team ensures they haven't just built a working piece of software, but the right piece of software for the audience's needs.

#### Further Reading

{% embed url="<https://www.geeksforgeeks.org/software-engineering/acceptance-testing-software-testing/>" %}

{% embed url="<https://agilealliance.org/glossary/acceptance-testing/>" %}

{% embed url="<https://www.virtuosoqa.com/testing-guides/what-is-acceptance-testing>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=sGwm4p9sGPI>" %}

{% embed url="<https://www.youtube.com/watch?v=JDD5EEJgpHU>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/ux-methods/testing/acceptance-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.