> 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/create-and-execute-tests-with-design-studio/optimizer-beta.md).

# Optimizer (Beta)

The Optimizer helps you review an Avo Assure project and identify areas for improvement. It uses prompts to check specific conditions across project areas such as Test Cases, Test Steps, Element Repository, Execution Lists, and Data Tables. For example, prompts can identify test steps with fixed wait times, unused artifacts, inconsistent execution results, or other items that require review. 

Optimizer provides two types of prompts:

* **Verified**: Provides predefined prompts for commonly required project analysis. These prompts are grouped into the following categories:
  * **Authoring Quality**
  * **Suite Health**
  * **Execution Health**
* **Custom**: Allows you to create a prompt based on a specific requirement.

You can run a prompt to view the results and use the available options to review and manage the identified items.

## Why Use Optimizer?

A project can contain a large number of Test Cases, Test Steps, Element Repository, Execution Lists, and Data Tables. Reviewing these items manually can make it difficult to identify items that require review or improvement.

Optimizer displays the items identified by the selected prompt, along with relevant details such as the project area, item name, and status. This helps you identify items that require cleanup or correction.

## Benefits

Optimizer helps you:

* Identify project items that require review.
* Find unused, empty, or unnecessary artifacts.
* Review test cases and test steps for common quality issues.
* Identify execution results that may require investigation.
* Review results by project artifacts.
* Take available actions on the identified items.
* Run checks manually or schedule them for regular review.

The results of each prompt are displayed with the identified items, allowing you to review the results and take the available actions.

{% hint style="info" %}
**Note**:  

* The current version of **Optimizer** is a **Beta** version and continues to be enhanced and refined based on customer feedback and usage.  
* Review all results carefully before taking any action on the identified items.
  {% endhint %}

## Prerequisites

The following requirements must be fulfilled before using the Optimizer in Avo Assure:

* **User Role**: Ensure you sign in as a Quality Manager, or as a Quality Manager with administrator rights. The Optimizer reads data from across your projects, so only these roles access it. 
* **Project Access**: Ensure you have access to the projects you want to review. The Optimizer returns result only from the projects available to you.
* **Test Assets**: Ensure your projects already contain test cases, element repositories, execution lists, and data tables. The Optimizer reports on the assets you have, so an empty project returns no result.
* **Completed Executions**: Ensure that the selected test cases have at least one completed execution for prompts that require execution data.

### Important Notes 

* Actions available for **Verified** prompts are final and cannot be reversed. The actions are recorded in the **Audit Logs**. 
* **Custom** prompts do not perform any actions. The results provided by **Custom** prompts may be inaccurate depending on the prompt.
* The **Failed to generate response** message may appear when Optimizer cannot generate a response with the required data.

{% hint style="warning" %}
Do not modify or execute artifacts while an optimization is in progress. Changes may cause conflicts or data loss.
{% endhint %}


---

# 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/create-and-execute-tests-with-design-studio/optimizer-beta.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.