> 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/create-test-case/create-test-step-group.md).

# Creating Test Step Group

You can create a Test Step Group using any of the following methods:

* [**Adding New Test Step Group**](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/create-test-case/create-test-step-group/add-new-test-steps-group.md)
  * Use this option to manually create a new Test Step Group from scratch.
  * You can add individual Test Steps.
  * Once completed, the Test Step Group can be saved and used within Test Cases.
* [**Adding Test Step Group from Reusable Library**](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/create-test-case/create-test-step-group/add-test-steps-group-from-reusable-library.md)
  * This option allows you to add an existing Test Step Group from the **Reusable Library**.
  * It helps in maintaining consistency and reusing frequently used test steps across multiple Test Cases.
  * Simply select the required Test Step Group from the library, and it will be added to your current Test Case.
* [**Adding Test Step Group using Avo Genius**](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/create-test-case/create-test-step-group/record-test-step-group-using-avo-genius.md)
  * Use this option to record Test Steps automatically using **Avo Genius**.
  * Actions performed during recording are captured as Test Steps in the group, including element selection, input values, and actions performed.
  * This method simplifies Test Step creation for dynamic or complex scenarios.


---

# 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/create-test-case/create-test-step-group.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.