> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/utilities-and-tools/odk-collection-app/user-guides/test-a-form.md).
# Test a Form
## Description
This document provides instructions to test a form available in a project using ODK Central.
## Prerequisites
* [ODK Central](https://docs.getodk.org/central-intro/) must be deployed and available
* A user must have valid credentials to login **ODK Central**
* A user must have an Administrator role in ODK Central. See [Create User and Assign Role](/1.3/pbms/functionality/administration/role-based-access-control/user-guides/assign-roles-to-users.md) guide
* A user must have ODK Collect App in his/her device
## Procedure
1. Login to the **ODK Central**
2. Click the relevant project link.
For example, here, the project is considered as Demo project
3. Click the project (Demo) link listed below the **Projects**.
ODK home screen
4. The project (Demo) overview page is displayed.
Uploaded form
5. Click the form available below the ***Forms***.
For example, here the form selected is AbhiBus Forms.
The AbhiBus Forms screen is displayed.
Forms screen
6. Click the ***test*** link available in the ***Draft Checklist*** below the option ***Test the form by creating a Submission***
The ***Draft Testing*** screen is displayed.
Draft Testing screen
7. Click ***+New*** button to preview the uploaded form.
8. Click the ***Testing*** tab in the ***Draft*** section.
9. ***Testing*** tab displays the QR code.
10. Tab the ***ODK Collect App*** in his/her mobile.
11. Tap the ***Configure with QR code*** button.
Add project screen is displayed.
12. Scan the ***QR code*** of a relevant form in a project from the ***ODK Central***.
The form is configured in the ***ODK Collect App***.
This completes the testing of the uploaded form.
---
# 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.openg2p.org/1.3/utilities-and-tools/odk-collection-app/user-guides/test-a-form.md?ask=&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.
