I have unit tests that get executed as part of my TFS 2015 build (created using the native Microsoft.VisualStudio.TestTools.UnitTesting assembly).
Everything worked fine. I upgraded TFS this morning to TFS 2015 v3. The upgrade went perfectly and no errors were encountered.
Running a subsequent build and the unit tests are no longer getting executed. I run these using a Visual Studio Test build step.
Looking into the build logs I have found that there are subtly different commands being executed for vstest.console.exe.
A working command (from yesterday before the upgrade)
vstest.console.exe
"E:\TfsData\Build\_work\DEV\CoreLibraryTests\bin\Release\CoreLibraryTests.dll"
/Settings:"E:\TfsData\Build\_work\DEV\CoreLibraryTests\CoreLibraryTests.runsettings"
/logger:trx
And here's one from today (that fails)
vstest.console.exe
"$/DEV/CoreLibraryTests/bin/Release/CoreLibraryTests.dll"
/Settings:"E:\TfsData\Build\_work\DEV\CoreLibraryTests\CoreLibraryTests.runsettings"
/logger:trx
In the failing build step the path "$/DEV/CoreLibraryTests/bin/Release/CoreLibraryTests.dll" has not been resolved to a physical path on disk (which it did previously - see working command).
This was all working and I can't understand why it's now failing. Any ideas how this can be fixed?