> 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/support-resources/tips-and-tricks/design-studio/test-case.md).
# Test Case
Use this section to learn tips and tricks for creating and managing Test Cases. These help you to organize test cases clearly, reuse steps where possible, and use test data effectively to make automation easier to manage.
Speed Up Test Design with Add from Repository
Use **Add from Repository (Drag and Drop)** to quickly add elements to your test case and automatically map the relevant actions, reducing manual effort and accelerating test creation.
Use Agent or Grid Execution for Large Test Suites
Run large test cases using **Agent** or **Grid Execution** to execute multiple test cases in parallel and reduce the overall execution time.
Use Scrollbar Elements for Reliable Grid Scrolling
For Microsoft Dynamics 365 grids, use the **scrollbar elements** with **Verify Exist** followed by **Click Element** instead of the **Scroll Vertical** or **Scroll Horizontal** grid actions to achieve more reliable vertical and horizontal scrolling during automation.
Verify the Tab State Before Interacting with Dynamics 365 Tabs
Check whether a **Dynamics 365** tab is expanded before interacting with its fields. If the tab is collapsed, expand it first to ensure all required fields are accessible and prevent execution failures.
Use Get Specific Object for Dynamic Web Elements
Use **Get Specific Object** to dynamically locate and store web elements as reusable reference objects, enabling reliable interaction with dynamic grids and complex UI structures without creating custom XPath expressions.
Validate UI Table Data Against Downloaded Excel
Use **Excel Actions**, **dynamic variables**, and **loops** to compare UI table data with downloaded Excel data row by row, ensuring accurate and scalable data validation.
---
# 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/support-resources/tips-and-tricks/design-studio/test-case.md?ask=&goal=
```
`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.