# Finding obsolete tests based on requirements

> You can identify obsolete test cases linked to requirements using Autopilot for Testers. Autopilot identifies obsolete test cases by analyzing their relevance to updated requirements, checking for deprecated functionality, redundant coverage, outdated environments or dependencies, and misaligned or unsupported test steps.
:::note
This capability is available only in Test Manager delivered via Test Cloud.
:::

You can identify obsolete test cases linked to requirements using Autopilot for Testers. Autopilot identifies obsolete test cases by analyzing their relevance to updated requirements, checking for deprecated functionality, redundant coverage, outdated environments or dependencies, and misaligned or unsupported test steps.
:::note
This capability is available only in Test Manager delivered via Test Cloud.
:::

## Prerequisites

To find obsolete test case linked to requirements, your Test Manager role must have the following permissions:

* **Requirement** - Edit
* **Test Case** - Edit

## Steps

To find obsolete test cases linked to requirements, follow these steps:

1. Open a project, and navigate to **Requirements**.
2. Select **More Options** for the desired requirement and choose **Optimize coverage**. Alternatively, open the requirement, and then choose **Optimize coverage**.
3. In the **Optimize coverage** dialog, select **Find obsolete tests**. The **Provide additional context** window opens, focused on **Add documents**, prompting you for attachments or other documents necessary for identifying the obsolete test cases.
   1. In the **Add documents** section, select the attachments you want to use when searching for obsolete test cases. You can upload other files yourself.
   2. Select **Next** and provide additional instructions that Autopilot should use when finding obsolete test cases. Choose a prompt from the [Prompt library](https://docs.uipath.com/test-manager/automation-suite/2.2510/user-guide/prompt-libraries#prompt-library) or type these instructions in the **Provide additional guidance** window.
   
   Optionally, from the **Model** dropdown list, select the AI model that Autopilot should use. Autopilot uses Claude 3.7 Sonnet by default when finding obsolete tests, which is also the recommended model.
         :::note
         The models available in the **Model** dropdown list depend on the [AI Trust Layer Policy](https://docs.uipath.com/automation-ops/automation-suite/latest/user-guide/settings-for-ai-trust-layer-policies) applied to your organization and tenant. If all supported models are enabled, Claude 3.7 Sonnet appears as the recommended option. If only one model type is enabled (for example, Azure OpenAI), then the GPT 4o model is the only one shown and automatically recommended.
         :::
         
   3. Select **Find obsolete tests** to initiate the process. When the find operation finished, you will receive an **Obsolete tests discovered** or a **No obsolete test cases discovered** notification. Depending on your [notification preferences](https://docs.uipath.com/test-manager/automation-suite/2.2510/user-guide/my-notifications#my-notifications), you can receive the notification both in-app and via email. You can then un-assign the resulted obsolete test cases, or add labels to them, depending on your needs.

      Figure 1. The Latest results for a requirement, including obsolete tests

      ![The latest results of a requirement, including obsolete tests](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-the-latest-results-of-a-requirement-including-obsolete-tests-574892-53c03310-c08d9b49.webp)