Closed JonHanna closed 7 years ago
Thanks, I reported the issue with vstest a couple of days ago https://github.com/Microsoft/vstest/issues/504
Nunit changing the way working directory works with it may be responsible.
I'm not in a huge rush to get this fixed - it only effects test runs from inside VS - the command line passes. I'm going to wait to hear whether vstest is going to fix it in the framework or not.
The vstest team has told me that they're fixing this issue in VS2017 Update 1. I'm going to wait for their fix.
Working directory can be set to e.g. C:\WINDOWS\system32 depending on how Visual Studio was opened, leading to the wrong path being used in the test.