For detailed information on creating data-driven tests, see Creating Data-Driven Tests.
The parent test created in this process does not have parameters associated with it, since it only represents a structuring instance for its child tests and no longer functions as an actual test. All values found in the data source will be listed in the parent test’s Data-driven Properties section.
When assigning a parent test to a requirement, links to requirements are only inherited when using atomic data-driven tests.
You can not assign the parent test of a non-atomic data-driven test to a setup or cleanup test execution, as such a parent node is treated as a folder. You can assign one of its child nodes though, and you can also assign an atomic data-driven test to a setup or cleanup test execution.
For detailed information on data source limits, see Data Source Limits.