> 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/knowledge-base-articles/dynamic-test-data-handling-at-runtime-execution.md).

# Dynamic Test Data Handling at Runtime Execution

**Summary**: This document explains the process of handling data during runtime from different test cases across various folders using variables 

### Error behavior

When this issue occurs, you may observe the following behavior:

* The data from the variable is not passed to different test cases at runtime.

### **Possible Reasons**

This issue may occur due to one or more of the following reasons:

* The correct variable names are not provided to dependent test cases 
* The variable declaration format is incorrect 
* The E2E flow is not created before adding test cases from different folders to the execution list 

### Resolution/Solution

To resolve the issue, perform the following action:   

1. ​​Check the variable names and formats passed across different test cases.  
2. Create the E2E flow and include all test cases from different folders. 


---

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

```
GET https://docs.avoautomation.com/avo-assure/support-resources/knowledge-base-articles/dynamic-test-data-handling-at-runtime-execution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.