> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/advanced-logic/automated-tests.md).
# Automated tests
Write automated tests to ensure your logic rules behave as expected.
Once you have created a logic rule, you may navigate to the **Tests** tab of the rule to set up automated tests for the rule that automatically run in an isolated environment when the form is published. If any test fails, the form will fail to publish.
For each of the tests, you'll want to specify:
* A unique test name
* The initial field values before the logic rule is run, formatted in a JSON object where the key is the field ID and the value is the initial value of the field.
* The expected state of field values after the logic rule is run, similarly formatted in a JSON object.
{% hint style="info" %}
Note that any network request or method on the **feathery** global object that's called from your logic rule will not actually run during the test and will simply be stubbed out.
{% endhint %}
Having comprehensive tests for your logic rules will allow you to be confident in the updates you make to your form while not needing to fall back on time-consuming manual validation for rule-related changes.
---
# 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.feathery.io/platform/build-forms/advanced-logic/automated-tests.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.
