> 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/3.7.0/developer-tools-and-resources/automation-testing/performing-ui-automation-testing.md).

# Performing UI Automation Testing

Following command is used to run all UI tests in an interactive dashboard that allows you to see the status of the tests while they are running and at the same time view the application under test.

```
npm run ui-only 
```

To run a UI test for specific policy you can open Cypress dashboard by running the following command from /e2e-tests folder:

```
npx cypress open 
```

After executing this command, you will see a welcome window where you need to select

'E2E Testing' as shown below:

<figure><img src="https://content.gitbook.com/content/p049ONtJzdmiKq7Lsv1e/blobs/X083wtZidDugZyiLigrL/image%20(7).png" alt=""><figcaption></figcaption></figure>

Click on the button ' Start E2E Testing in Electron '.

<figure><img src="https://content.gitbook.com/content/p049ONtJzdmiKq7Lsv1e/blobs/nxNQo7Oxa7FXKnym2O3y/image%20(9).png" alt=""><figcaption></figcaption></figure>

and then select test under ui-tests/specs/policies

<figure><img src="https://content.gitbook.com/content/p049ONtJzdmiKq7Lsv1e/blobs/6DnAUG5pNtrO9ztm8nr5/image%20(8).png" alt=""><figcaption></figcaption></figure>

Finally, all the selected test runs and you can see the key components of the Test Runner that you need to pay attention to when executing tests.

<figure><img src="https://content.gitbook.com/content/p049ONtJzdmiKq7Lsv1e/blobs/5sUYBCGpLhYhIBogkyBl/image%20(2)%20(1)%20(1)%20(3).png" alt=""><figcaption></figcaption></figure>

**Test Status Menu:** The menu shows a summary of the number of tests pending, passed, failed, or incomplete, and the time spent on the test.

**URL Preview:** Shows the URL of the test, helps track the URL.

**Viewport Size:** Set the size of your application's viewport to test responsive web applications.

**Command Log:** Shows command logs as they run for all tests. In Cypress runner we can observe the requests that are sent to the server.

**App Preview Screen:** You can see the app while the test is running.


---

# 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://guardian.hedera.com/docs/3.7.0/developer-tools-and-resources/automation-testing/performing-ui-automation-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.
