> 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/prompts/working-with-verified-prompts.md).

# Working with Verified Prompts

The Verified prompts provide predefined checks for reviewing different areas of an Avo Assure project. The prompts are grouped into Authoring Quality, Suite Health, and Execution Health, with each category covering specific types of project items and execution data. The results of a prompt display the project items that meet the conditions defined by that prompt, along with the details and actions available for those items.

This article explains how to run Verified Prompts and view their results. It also describes the categories, prompts, conditions checked by each prompt, and actions available for the results.

The Verified prompts are grouped into the following categories:

* **Authoring Quality**
* **Suite Health**
* **Execution Health** 

## Authoring Quality

The Authoring Quality prompts provide predefined checks to review how different project artifacts are created and maintained. The prompts cover artifacts such as Test Cases, Element Repository, Execution Lists, and Data Tables.

The following prompts are available under **Authoring Quality**: 

<table><thead><tr><th width="148.6666259765625">Prompts</th><th width="290">Description</th><th>Result</th></tr></thead><tbody><tr><td><strong>Contains static waits</strong>  </td><td>Identifies test cases that contain fixed wait times before the next step runs.  </td><td>Displays the test cases and steps that contain static waits. Use <a href="/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md#replacing-static-waits"><strong>Replace all static waits</strong></a> or <strong>Replace selected static waits</strong> to replace applicable static waits with dynamic waits and the changes reflect in the Test Case.  </td></tr><tr><td><strong>Hardcoded test data</strong>  </td><td>Identifies test cases that use fixed values instead of data parameterization.  </td><td>Displays the test cases and test step groups that contain hardcoded values. Review the listed test cases in the result table and change them accordingly.  </td></tr><tr><td><strong>Step runtime outliers</strong>  </td><td>Identifies test steps that take more than 3 seconds to run.  </td><td>Displays the test steps with higher run times. Review the execution time of the listed test steps in the result table.  </td></tr><tr><td><strong>Non-compliant names</strong>  </td><td>Identifies folders, element repositories, test cases, and elements that do not follow the naming standards.  </td><td>Displays the items with non-compliant and suggested names. Select the required items and use <a href="/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md#updating-artifact-names"><strong>Suggest and rename</strong></a> to update with suggested names from the result table.  </td></tr><tr><td><strong>Flaky test cases</strong>  </td><td>Identifies test cases whose execution results change between runs even when the test case remains unchanged.  </td><td>Displays the test cases with inconsistent execution results. Review the execution results to understand the changes from the result table.  </td></tr></tbody></table>

## Suite Health

The Suite Health prompts help you identify project artifacts that are unused, empty, stalled, or not referenced by other artifacts. These prompts cover Element Repositories, Test Cases, Execution Lists, and Data Tables.

The following prompts are available under **Suite Health**:

<table><thead><tr><th width="149.3333740234375">Prompts</th><th width="290">Description</th><th>Result</th></tr></thead><tbody><tr><td><strong>Orphaned artifacts</strong>  </td><td>Identifies artifacts that have no assignee or have an inactive assignee.   </td><td>Displays the identified artifacts. Use <a href="/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md#reassigning-artifacts"><strong>Bulk Reassign</strong></a> to assign them to an active user.  </td></tr><tr><td><strong>Unexecuted test cases</strong>  </td><td>Identifies test cases that are not executed.  </td><td>Displays the identified test cases. Use <a href="/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md#deleting-identified-items"><strong>Delete All</strong> </a>or <strong>Delete Selected</strong> to remove test cases that are no longer required.  </td></tr><tr><td><strong>Empty artifacts</strong>  </td><td>Identifies empty <strong>Element Repositories</strong>, <strong>Test Cases</strong> without test steps, <strong>Execution Lists</strong> without test cases, and <strong>Data Tables</strong> without data.  </td><td>Displays the identified artifacts. Use <strong>Delete All</strong> or <strong>Delete Selected</strong> to remove artifacts that are no longer required.  </td></tr><tr><td><strong>Stalled artifacts</strong>  </td><td>Identifies <strong>Element Repositories</strong>, <strong>Test Cases, Execution Lists</strong>, and <strong>Data Tables</strong> whose status does not change for more than 60 days.  </td><td>Displays the identified artifacts. Use <strong>Delete All</strong> or <strong>Delete Selected</strong> to remove artifacts that are no longer required.  </td></tr><tr><td><strong>Project-wide reference gaps</strong>  </td><td>Identifies artifacts that are not used by any other artifacts in the project.  </td><td>Displays the identified artifacts. Use <strong>Delete All</strong> or <strong>Delete Selected</strong> to remove artifacts that are no longer required. </td></tr></tbody></table>

## Execution Health

The Execution Health prompts allow you to check the execution results and behavior. They help identify frequently terminated test case executions, duplicate execution entries, and changes in execution time.

The following prompts are available under **Execution Health**:

<table><thead><tr><th width="149.3333740234375">Prompts</th><th width="289.99993896484375">Description</th><th>Result</th></tr></thead><tbody><tr><td><strong>Frequently terminated tests</strong>  </td><td>Identifies test cases that have a high number of terminated runs in the last 30 days.  </td><td>Displays the test cases with the highest number of terminated runs. Review the execution in the results table.  </td></tr><tr><td><strong>Duplicated execution entries</strong>  </td><td>Identifies <strong>Execution Lists</strong> that contain the same test case more than once.  </td><td>Displays the Execution Lists with duplicate Test Case entries. Review the entries in the result table and use <a href="/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md#removing-duplicate-test-cases"><strong>Remove test case from execution list</strong></a> to remove the duplicate Test Cases.</td></tr><tr><td><strong>Runtime regressions</strong></td><td>Identifies <strong>Execution Lists</strong> where the execution time increases across the last 5 completed runs.</td><td>Displays the execution lists with the highest increase in elapsed time across their last 5 completed runs, where the test case set remains the same. Review the execution time in the result table to identify increases across runs. </td></tr></tbody></table>


---

# 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/prompts/working-with-verified-prompts.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.