> 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/add-new-test-steps-group.md).

# Adding New Test Step Group

A Test Step Group helps you organize related test steps within a test case, making it easier to manage and reuse. This article describes how to add a new test step group to a test case.

To add a Test Step Group to a Test case, perform the following actions:

1. On the **Home** page, under **Projects**, select the required Project.
2. Select **Design Studio** > **Test Case**. 
3. In the **Test Cases** pane, select the test case folder.
4. Select the test case for which you want to add the test step group.
5. Select **Create Test Step Group** > **Add new test step group**. The **Test Step Group** dialog opens.
6. In the **Test Step Group Name** text box, enter the test step group name.
7. From the **Application Type** dropdown, select the required **Application Type**.
8. Select **Create** to add a new test step group. This creates a new test step group inside the test case. 

{% hint style="info" %}
**Note**: You can also add a Test Step Group from the [Reusable Library](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/reusable-library.md).
{% endhint %}

9. Add test steps to the test step group using one of the following options: 

<details>

<summary>Add from Repository</summary>

To add elements from the Element Repository to the Test Step Group, perform the following actions:

1. In the **Test Step Group**, select **Add from Repository**. The **Element Repository** pane opens.
2. From the **Element Repository** pane, drag the required elements and drop them into the selected **Test Step Group**.&#x20;

{% hint style="info" %}
**Note**: When you drag and drop the elements to the Test Step Group, the corresponding actions are added automatically to the test steps.
{% endhint %}

3. Select **Save** to save the test steps.&#x20;

{% hint style="info" %}
**Note**: You can edit the test steps after adding all the required elements to the Test Step Group.
{% endhint %}

</details>

<details>

<summary>Add Manually</summary>

To add elements manually to the Test Step Group, perform the following actions:

1. In the Test Step Group, select **Add Manually**. A new test step is added to the Test Step  Group.
2. From the **Elements**, select the required values.&#x20;
3. To add another test step, select the **Add Step** (**+**) icon, and then select **Add step** manually.
4. Select **Save** to save the test steps.

</details>

9. Select **Save** to save the test steps to the test step group.


---

# 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/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?ask=<question>&goal=<endgoal>
```

`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.