> 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.md).

# Creating Test Case

A test case in Avo Assure defines the sequence of test steps required to validate a specific test scenario. This article describes how to create a test case within a project, including creating the folder structure and adding the test step group.

To create a new Test Case in Avo Assure, perform the following actions:

1. On the **Home** page, under **Projects**, select the required Project.
2. Select **Design Studio** > **Test Case**.
3. On the **Test Case** page, locate and select the **Create Folder** (**+**) icon.
4. Select **Create main folder** to create a new test case folder. A new folder is created.
5. In the **New Folder** text box, enter the test case folder name.
6. In the newly created folder, select the **See more** (**...**) icon next to the test case folder name.
7. Select **Create test case** to create the test case.
8. In the **New Testcase** text box, enter the test case name.
9. Select **Create Test Step Group**, and then choose one of the following options to add test steps to the test case:&#x20;
   * [Adding New Test Step Group](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)
   * [Record Test Step Group Using Avo Genius](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/record-test-step-group-using-avo-genius.md)
   * [Paste test step group](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section/copy-and-paste.md)

{% hint style="info" %}
**Note**: You can also add test step group from [Reusable Library](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-test-steps-group-from-reusable-library.md).
{% endhint %}

10. Select **Save**. The test case is created with the configured test step group.

### **Example: Creating a Login Test Case from Start to Finish**

This example demonstrates how to create a Test case that logs in to a web application. It covers capturing web elements in the Element Repository, creating a Test case, adding a Test step group, and configuring the Test steps.

1. On the **Home** page, under **Projects**, select required project from list.
2. Go to **Design Studio** > **Element Repository**.
3. Capture the login page elements in the Element Repository:
   * **Username**: Username input box.
   * **Password**: Password input box.
   * **Login**: Login button.

{% hint style="info" %}
For more information, see [Creating Web Element Repository](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/create-element-repository/capturing-web-elements.md).
{% endhint %}

4. Select the **Test Case** tab to create a Test Cases for captured elements.
5. Create a folder and a Test Case named **Login**.
6. Create a Test Step Group:
   1. Select **Create Test Step Group** > **Add new test step group**.
   2. Enter **Login** as the Test Step Group name.
   3. Select **Web** as the application type.
   4. Select **Create** to create the **Login** Test Step Group.
7. Add the following Test steps to the group:

<table><thead><tr><th width="55.16668701171875">Step</th><th width="106.3333740234375">Elements</th><th width="148.5">Actions</th><th>Input Value</th></tr></thead><tbody><tr><td>1 </td><td>Browser </td><td>Open Browser </td><td>N/A </td></tr><tr><td>2 </td><td>Browser </td><td>Navigate to URL </td><td><a href="https://avogo.avoautomation.com/">https://avogo.avoautomation.com</a> </td></tr><tr><td>3 </td><td>Username </td><td>Set Text </td><td>JohnDoe </td></tr><tr><td>4 </td><td>Password </td><td>Set Secure Text </td><td>{"iv":"nueWjOAluJFCR6O4","encrypted":"Qn8nP+LYB/i65nmLMBn/6w==","authTag":"DbIgeo0cUviW8NaTDcoH5g=="} </td></tr><tr><td>5 </td><td>Login </td><td>Perform Click </td><td>N/A </td></tr></tbody></table>

8. Select **Save** to save the Test Case.
9. Select [**Debug**](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) to execute the Test steps and verify that each step passes

{% hint style="info" %}
**Note**: Use [**Set Text**](https://docs.avoautomation.com/avo-assure/actions/web/textbox/set-text.md) to enter a normal password and [**Set Secure Text**](https://docs.avoautomation.com/avo-assure/actions/web/textbox/set-secure-text.md) to enter an [encrypted](https://docs.avoautomation.com/avo-assure/utilities/encryption.md) password.
{% endhint %}

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FPox7dQDi7N0jHg2vMyy8%2Funknown.png?alt=media&amp;token=bd8a3e34-d1a8-4af0-bb30-0564e3e4cb99" alt="" height="281" width="626">


---

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