> 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/record-test-step-group-using-avo-genius.md).
# Record Test Step Group Using Avo Genius
To record test step group using Avo Genius follow the steps:
### Design Studio
**Web Application**
1. Click on **New test step group** and select **Record new test step group**
2. Avo genius window will pop-up. Select **Application type as WEB** and **Provide Application URL. Click Start Recording.**
3. Avo Genius recording window will pop up. Click on the elements to add them
4. Click on Finish and save.
5. All elements will be captured in the test step group
### FOR SAP
1. Click on **New test step group** and select **Record new test step group**
2. Avo genius window will pop-up. Select **Application type as SAP** and **Provide Application Path. Click Start Recording.**
3. Avo Genius(SAP) window will pop up with another window to enter username and password.
4. Once recording is complete. Provide Folder name and testcase name and Click Save.
5. All Elements will be saved in the test Case step.
---
# 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/record-test-step-group-using-avo-genius.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.
.png?alt=media&token=71d79b3a-2041-4ed7-99ea-f584ab90c44c)
.png?alt=media&token=369c485c-1f6f-462a-bd28-c3bc727fab08)
.png?alt=media&token=d4d23788-fa84-4f42-8d18-c9d5bbade978)