This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 74%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
I have a test case (MS UnitTest Framework, VS 2019) that uses the [DataTestMethod] [DynamicData(nameof(GetTestData), DynamicDataSourceType.Method)] attributes to iterate thru several objects. Running the test in VS TestExplorer works great, it iterates thru all the rows being passed (works like a champ). However, when I run the same test case from the command console using dotnet or vstest.console runners, it executes the test only once.
Am I missing something?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello Neftali, thank you for posting here. May I ask how do you know that the test only executed once but didn’t iterate through all the rows being passed like running in Test Explorer? For vetest.console.exe, it runs tests and displays the test results of each test method. You can try to add /logger:trx to log and analyze more detailed information of test results.
Besides, could you please share more information such as some code snippets and reproduced steps with me for further check?
Thanks for the quick response. After going back to review, I realized it was my own fault. I was using only two rows for a quick test, however, on incrementing the rows I was starting the count of rows at 1 instead of zero (a stupid mistake because I wanted my count to start at 1 for other reasons). Because the count was starting at 1, it was omitting to run the test case for row 0.
Hi Neftali, really glad to hear that you find the cause of this issue and I appreciate that you share the solution(the cause) with us. You can accept your reply as answer, and this will be helpful for other members who have similar issues to easily find and check this thread. Have a nice day : )