I’m attempting to run unit tests from the command line. I tried using the mstest.exe program using the following command:
E:/VS Projects/.../>"C:/Program Files (x86)/Microsoft Visual Studio 11.0/ Common7/IDE/MSTest.exe" /testcontainer:mytest.dll /testsettings:"E:/VS Projects/.../Local.testsettings"
The mstest program responce was:
Microsoft (R) Test Execution Command Line Tool Version 11.0.50727.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading E:/VS Projects/.../Local.testsettings... Loading mytest.dll... mytest.dll Unable to load the test container 'mytest.dll' or one of its dependencies. If you build your test project assembly as a 64 bit assembly, it cannot be loaded. When you build your test project assembly, select "Any CPU" for the platform. To run your tests in 64 bit mode on a 64 bit processor, you must change your test settings in the Hosts tab to run your tests in a 32 bit process. Error details: Could not load file or assembly 'file:///E:/VS Projects/.../mytest.dll' or one of its dependencies. The module was expected to contain an assembly manifest.
Local.testsettings does include information, that the tests shall be run in 64-bit environment.
I can guess, that mstest expects an assembly instead of native test project and this is why it fails. If so, how can I run native tests from the command line? In the other case, how shall I configure the mstest to work properly?
Running unit tests from within VS2008 vs using mstest on the command line
I have recently encountered some inconsistencies in running unit tests inside VS2008 vs running the same unit tests with mstest on the command line. My scenario is a bit advanced, so I have probably h
Running iOS Unit Tests from Command Line with Xcode 4.5
While running Unit Tests from command line (necessary for Jenkins) used to work until Xcode 4.4.1 with this hack, it does not seem to work anymore with Xcode 4.5. Now I get the following error message
running mstest from command line against visual studio 2012 native c++ tests
I have a Visual Studio 2012 Solution with a number of native c++ test projects. I can run all of these correctly and successfully from within Visual Studio 2012 using the Test Explorer tab. However, I
Error running Xcode Unit Tests from Command Line
I am trying to run my Xcode unit tests via command-line so I can eventually wire it to Jenkins for CI. The Workspace contains 2 projects: CommonProject (shared libraries used for multiple apps) MainPr
Running unit tests from the command line fail after upgrading to Xcode 5.1
After upgrading to Xcode 5.1, running unit tests from the command line stopped working. Here is what happens when I run xcodebuild test -workspace MyApp.xcworkspace -scheme MyApp -sdk iphonesimulator
Error running ‘Cedar’ unit tests from command line
I’m using the cedar testing framework and trying to run the tests from command line. The build crashes with this error: Unresolved error Error Domain=NSCocoaErrorDomain Code=512 The operation couldn’
Running android unit tests from the command line?
I’m trying to run unit tests on the android platform in accordance with tutorial. Say, for example, I want to run tests for Email application. I open /apps/Email/tests/AndroidManifest.xml file, look f
Issue running iOS unit tests on command line (OCUnit + OCMock)
I’m trying to get unit tests to run in CI (Jenkins). I came across this a article online with some hacks to get tests running in command line. I tried it on an empty project with the default setup for
Set command line arguments in unit tests in C#
Is there a possibility to set the command line arguments in unit tests in VS2012? If not, is there an alternative to test many combinations of such arguments besides writing a batch file? EDIT: I have
Developer Licence error when running WinRT unit tests using vstest.console.exe from the command line
I’m getting the following error when I try to execute WinRT MSTests from the command line: EXEC : error : Could not start test run for unit tests for Windows Store app: No valid developer license foun
Thanks for Hans Passant for guidance.
The solution is to use:
C:/Program Files (x86)/Microsoft Visual Studio 11.0/Common7/IDE/CommonExtensions/Microsoft/TestWindow/vstest.console.exe