> 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/introduction-to-avo-assure/commence-avo-journey.md).

# Commence Avo Journey

This journey will guide you through the key sections of our Automation Testing Tool, helping you explore its functionalities in a logical sequence.

**1. Home Page**

Upon logging in for the first time, you'll be greeted by the [Home page](/avo-assure/introduction-to-avo-assure/exploring-home-page.md). Here, you’ll find an overview of your projects, quick links to essential features, and updates about new functionalities. This is your starting point for navigating the tool.

**2. Element Repository**

Next, head to the Element Repository. This section allows you to manage and organize UI elements for your tests. You can add, edit, or delete elements, making it easier to reference them in your test cases. Visit: [Element Repository](/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section.md)

**3. Test Cases**

Once your elements are in place, navigate to the Test cases section. Here, you can create and manage your test cases, incorporating the elements you've defined. This is where you’ll spend a lot of time designing and refining your test cases. Visit: [Test cases](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section.md)

**4. Execution**

After setting up your test cases, proceed to the Execution section. This is where you can run your tests and monitor their progress. You'll see real-time feedback on test results, helping you identify any issues immediately. Visit: [Execution](/avo-assure/create-and-execute-tests-with-design-studio/working-with-execution-section.md)

**5. Reports**

Finally, review the Reports section. Here, you'll find detailed analytics and reports on your test executions, providing insights into the test cases. This section helps you make informed decisions for future testing. Visit: [Reports](/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section.md)

**6. Dashboard**

The Avo Assure Dashboard provides a visual summary of your test executions with interactive graphs and metrics. Customize the dashboard to suit your needs and get detailed insights into your test results. [Dashboard](/avo-assure/introduction-to-avo-assure/exploring-home-page/managing-home-page/dashboard.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 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/introduction-to-avo-assure/commence-avo-journey.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.