> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/developer-tools-and-resources/automation-testing.md).

# Automation Testing

How automated tests validate Guardian services, APIs, and user interfaces.

Automation testing verifies that Guardian code changes preserve expected behavior. It runs repeatable checks before changes are released.

{% hint style="info" %}
This article covers automated checks for the Guardian codebase. It does not cover policy authoring tests.
{% endhint %}

#### The problem it solves

Guardian combines services, APIs, and user interfaces. A change in one component can affect another component.

Manual checks are slow and inconsistent. Automated tests detect regressions early and provide repeatable release feedback.

#### How it works

The codebase uses focused unit tests and end-to-end suites. Unit tests validate service behavior in isolation.

End-to-end tests exercise workflows across the running application. The `e2e-tests` directory contains Cypress-based UI and API automation.

These suites verify API responses, user interactions, and cross-service behavior. They support development and release validation.

#### Key distinctions

Automation testing validates the Guardian codebase and its integrations. It tests whether application changes behave correctly.

[Policy Integrity Tests](/docs/develop/guardian/workspace/policies/dry-run/policy-integrity-tests.md) validate declared policy inputs and outputs. They test a policy's behavior, not the Guardian codebase.

[Dry Run mode](/docs/3.6.0/guardian/standard-registry/policies/dry-run.md) simulates policy execution without affecting live systems. It supports safe workflow testing with virtual users and local artifacts.

Automation suites can use dry-run scenarios when validating policy flows. Dry Run mode is not the codebase test framework.

#### Related

* [Performing API Automation Testing](/docs/develop/developer-tools-and-resources/automation-testing/how-to-perform-api-automation-testing.md)
* [Policy Integrity Tests](/docs/develop/guardian/workspace/policies/dry-run/policy-integrity-tests.md)
* [Dry Run Mode Reference](/docs/3.6.0/guardian/standard-registry/policies/dry-run/demo-guide-on-dry-run-operations.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/docs/develop/developer-tools-and-resources/automation-testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.