> 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/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases.md). # Re-run Failed Test Cases The **Re-run Failed Test Cases** feature in Avo Assure is designed to improve test execution efficiency by allowing users to automatically re-execute only the test cases that failed in an execution profile during execution. Instead of rerunning the entire execution profile, this feature targets re-running failed test cases, saving time and resources while providing faster feedback and higher reliability in identifying genuine issues. ### This documents includes: 1. [**Feature and Capabilities**](/avo-assure/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases/feature-and-capabilities.md)\ Get more information about Re-run Failed Test Case feature and capabilities 2. [**Re-run failed Test Cases**](/avo-assure/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases/re-run-the-failed-test-cases.md)\ Steps to use Re-run failed Test Cases feature in Avo Assure 3. [**Best Practices**](/avo-assure/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases/best-practices.md)\ Best Practices to use Re-run feature in Avo Assure --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.avoautomation.com/avo-assure/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.