We've observed an odd behaviour where data driven tests set up with local data seem to only execute the first iteration when using the "run to here" and "run selected steps" options. According to the log, it correctly identifies the test as being data driven, identifies that it is executing the first iteration but does not execute any further iterations. (No errors or failures of subsequent iterations are present in the log). This occurs regardless of if the test is run as a standalone test, or a test-as-step in a larger test (in which case, after running the first iteration of the sub-test, the next step in the parent following the test-as-step runs (and fails on a data validation error since the other iterations did not execute).
On further analysis we determined that if the entire test is fully executed, it does seem to find and run all iterations of the subtest, so it seems only the partial run options seem to be encountering the issue.
We're unsure if this is by design, or if there is a configuration setting that may control only 1 iteration running when using the other run options.
Thanks,
Jeff Harrison
