Here is the answer in the ticket that you cannot see:
If a parent test is reading and creating its own Dataset object, the only way for a child test to get the data is if the parent test stores the data in some sort of a global variable/object that the child test can refer to, but it could only get at it from the coded steps of the child test. You won't be able to use the standard Test Studio data driven approach for non-coded steps.
I am thinking you'd be better off implementing your own Execution Extension DLL
. This DLL "extends" the functionality of Test Studio tests. All hooks contained in this DLL will get called always, by every test in every project ever run on that machine.
The hook you're after is this one:
public System.Data.DataTable OnInitializeDataSource(ExecutionContext executionContext)
Here you create your own DataTable object and Test Studio will use it as the data source for all data driven tests. In the ExecutionContext is the name of the test. You can optionally filter by the name of the test and adjust what you do. Returning NULL tells Test Studio to revert to its default behavior. The key advantage of taking this approach is that your child tests can use the InheritParentDataSource test property
and consume the data in the standard Test Studio fashion.
Hope that helps.
Telerik by Progress