> 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/working-with-test-case-section/features-in-test-case-section-1/debug-test-case.md).
# Debug Test Step Groups
The Debug allows you to execute selected test steps or test step groups to identify errors and verify their execution results. This article explains how to debug test step groups
To debug test steps, perform the following actions:
1. Locate to the **Test Case** page.
2. Select the required [created Test Case](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/create-test-case.md).
3. In the **Test Case** pane, select **Debug**. The **Debug** dialog opens.
4. Select the checkbox for the required **Test Step Group**, or select **Select Teststep Group(s)** to select all test step groups.
{% hint style="info" %}
**Note**: Select **Select Teststep Group(s)** again to clear all selections.
{% endhint %}
5. Select **Debug** to start the execute your Test Step Groups.
{% hint style="info" %}
**Note**: You can navigate to other tabs or make changes to the testcase while debugging. The changes take effect during the next debug.
{% endhint %}
After debugging completes, you can view the debug status on the **Avo Assure Client**.
---
# 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/working-with-test-case-section/features-in-test-case-section-1/debug-test-case.md?ask=&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.
