> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/get-involved/how-to-help-with-testing.md).

# How to help with Testing

One of the biggest bottlenecks that stops us releasing more features more quickly is the lack of people prepared to test features that are either already in the beta version or are ready for merging into the beta version ("pull requests").

## Testing the Beta version

The beta version is *usually* fairly solid but testing is invaluable - especially if you use Open Brush in depth (our testing is often from the perspective of a casual user) or you use a headset other than a Quest 2 (currently we do the bulk of our testing using Quest 2 via Link or standalone. Testing intesively on a wide range of headsets is a major chore).\
\
The best way to help test is to switch to using it instead of the normal version of Open Brush and to tell us what you find in the [Open Brush Discord](https://discord.openbrush.app). You can report a bug, suggest an improvement, or simply describe how a new feature feels to use. If you are not sure whether something is worth reporting, please mention it anyway.

To help you focus on testing the right things you can see a list of [changes and new features in the beta version here.](/release-history/automatic-changelog.md)

## Testing Pull Requests

"Pull Requests" are simply requests to pull in a new feature or bug fix to the main codebase. Once a pull request is approved it's automatically released as part of the current beta version.

Testing new features is a bottleneck for us at the moment We need feedback on the feature itself and help finding bugs that are serious enough for us to fix before merging in to the beta release.

In return you'll get to try out the real cutting edge features first and potentially influence the design choices we make.

On Github there is a list of [open pull requests](https://github.com/icosa-foundation/open-brush/pulls?q=is%3Apr+is%3Aopen+-is%3Adraft+). You can click on any one and then scroll down to the bottom:

![](https://3738774261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mikdwm98p33AibfiSqN%2Fuploads%2Fgit-blob-d08c8a96c241103772ba6c7699b8e383518c42a5%2Fimage-050.png?alt=media)

Click on any of the blue "details" links and then click "Summary" on the left followed by the number underneath "Artifacts" on the right:

![](https://3738774261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mikdwm98p33AibfiSqN%2Fuploads%2Fgit-blob-ceaed765208fb67d00bd532b87eb3e20bb980493%2Fimage-043.png?alt=media)

You'll then be taken to the bottom of the page where there is a list of all the builds:

![](https://3738774261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mikdwm98p33AibfiSqN%2Fuploads%2Fgit-blob-15183db4001ce88eb9b2411cec90f1b20c98c672%2Fimage-093.png?alt=media)

Just click on the name that matches your headset and it will begin to download a zip file.

(You might need to sign-up/sign-in to Github first)

## Testing Experimental Builds

[Experimental builds](/alternate-and-experimental-builds.md#beta-release) are the real bleeding edge. Some of the features might never make it into the official release. They can vary from "nearly ready" all the way to "barely working".

However - early on in the development of a new feature is when feedback is most likely to be useful and most likely to alter the direction a feature takes. These are the builds you want to be testing if you want to have a say in Open Brush development.


---

# 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://docs.openbrush.app/get-involved/how-to-help-with-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.