> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/design-studio/execution.md).

# Execution

Use this section to learn tips and tricks for test execution. These help you to run test cases, monitor execution, manage reruns, and use logs and failure details to ensure reliable automation runs

<details>

<summary><strong>Rerun Only Failed Test Cases</strong></summary>

Rerun only the failed test cases instead of executing the entire test suite again to verify fixes faster and reduce overall execution time.

</details>

<details>

<summary><strong>Optimize Test Execution with Headless Mode</strong></summary>

Use **Headless Execution** for faster, resource-efficient automation, and improve execution stability by using browser-specific keywords, dynamic waits, and validating execution screenshots.

</details>


---

# 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://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/design-studio/execution.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.