Mstest exe exited with code



Keywords: mstest exe exited with code
Description: I am manually running tests from msbuild/tfsbuild by manually invoking mstest.exe but it is failing unexpectedly with error MSB3073 and ExitCode 1 when I am expecting 0. I have this target that

I am manually running tests from msbuild/tfsbuild by manually invoking mstest.exe but it is failing unexpectedly with error MSB3073 and ExitCode 1 when I am expecting 0.

I have this target that searches for all DLLs with a postfix of *UnitTests.DLL in the $(OutDir) folder. It builds up a commandline statement that is then executed:

I've added a Timeout property above because some googling suggested this but it didnt make a difference.

This gets equated in the buildlog file as below (quotes included) (the folders names I have changed but left spaces where relevant but they don't look too long):

The tests DO run on the build server as part of the build process (i.e. calling the target above) as I can see the test results folder get created on disk. All unit tests pass as expected. I can see the MSTest.exe console output in my build log as well (e.g. Starting execution, list of tests and results, the results file is listed etc)

Additionally I can RDC onto the build server as the build service account and manually run the commandline above using a CMD and it works. (the test results (*.trx) and folder are there).

They also work when I manually invoke the commandline above using CMD them on my local developer machine as myself. It creates the test results file and folders.

FYI We are using Visual Studio 2012 Ultimate on my local machine and installed on the build server as well.

I've got a feeling its to do with the "parsing"/escaping of quotes and/or apostrophes or could it be the use of using. \ in the paths?

I have checked the event log on the build server and it displays no errors/information. Is there any other logs I can check? or properties I can define to "see" the actual error code?

NOTE: I know I could use the <RunTest> style msbuild/tfs build syntaxbut I manual trigger these tests at a more convenient time in the build process






Photogallery Mstest exe exited with code:


TeamCity | Degree Blog


JetBrains TeamCity Blog | Innovative Continuous Integration ...


Umbraco - Make TeamCity respect failing NUnit tests and stop the build


Visual Studio | Greycastle


Umbraco - Make TeamCity respect failing NUnit tests and stop the build


TeamCity | Degree Blog


Code coverage tool for .NET :: dotCover


Getting Typemock Isolator running within a TFS 2012 build


Visual Studio | Greycastle


Visual Studio | Greycastle


Dejan Dakic


Visual studio performance testing quick reference guide 3 6


MSBuild is now part of Visual Studio! - The Visual Studio Blog ...


May | 2012 | Replica of 'But it works on PC!' http://blogs ...


But it works on my PC! | The random thoughts of Richard Fennell on ...


But it works on my PC! | The random thoughts of Richard Fennell on ...


Playground for the mind


Code coverage tool for .NET :: dotCover