> 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/reusable-library/detaching-reusable-library-from-test-case.md).

# Detaching Test Step Group from Reusable Library

You can detach a test step group that was previously added to your Reusable Library. Detaching removes the link between the test step group and the Reusable Library, without deleting the test step group from the test case. This article describes how to detach a test step group from a folder under Reusable Library.

To detach a test step group from a reusable library, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case**.
3. In the left pane, under the **Test Cases** section, select the required test case folder.
4. Select the test case, and then select the test step group that you want to detach from the Reusable Library. The associated test steps appear.
5. Select the **Detach** icon. The **Confirmation** dialog opens.
6. Select **Yes** to detach the test step group from the reusable library.


---

# 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/reusable-library/detaching-reusable-library-from-test-case.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.