> 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/faqs/design-studio/execution.md).

# Execution

Use this section to view common questions related to test execution. It includes queries about running test cases, running test cases, execution controls, and different execution scenarios.

* **Can I execute test cases from the Execution section in Avo Assure?**

  **Ans**: Yes. You can execute test cases from the **Execution** tab by creating an execution list and selecting the required configuration. Once the configuration is set, you can select **Execute** to start the test run.
* **Is it possible to execute multiple test cases in a single execution run?**

  **Ans**: Yes. Multiple test cases can be added to an [execution list](/avo-assure/create-and-execute-tests-with-design-studio/working-with-execution-section/creating-execution-list.md) and executed together in one run to validate several scenarios at the same time.
* **Is it possible to monitor execution status from the Execution tab?**\
  **Ans:** Yes. **Execution** tab provides visibility into the execution status and shows whether a test run is **Passed**, **Failed**, **Terminated**, **In Progress**, or **Queued**.
* **Can I schedule test execution to run automatically?**

  **Ans**: Yes. Using the [Scheduler](/avo-assure/create-and-execute-tests-with-design-studio/working-with-execution-section/execute-execution-list/scheduler.md), you can set a start date, end date, and recurrence pattern so the execution runs automatically at the scheduled time.


---

# 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.avoautomation.com/avo-assure/support-resources/faqs/design-studio/execution.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.