Skip to main content

Running unit tests using MSTest from console application

There are times when you end up with a requirement like this:
You should be able to run Unit Tests from console application.
And yes, we are talking about MSTests. Well, this is not very complicated using MSTest.exe
Mstest  /testcontainer:[pathToOurTestComponent.dll]
After a few day you end up with a new requirement:
Run Unit Tests using a console application from a machine that doesn’t  
have Visual Studio installed
Using different scripts from internet (like this one: http://mindinthewater.blogspot.ro/2011/02/executing-visual-studio-2010-unit-tests.html), you end up with a configuration that can be used to run unit tests on machines that doesn’t have Visual Studio.
Mission complete? Yes.
But, you have a problem. Yes, there is a but. What about licensing? Are you allowed to do something like this?
Depends of the person who run your console application. You are allowed to do something like this as long the person who run the console application has a Visual Studio license. This is needed because MSTest component is not allowed to be redistributed based on the current license.
What should I do if clients don’t have a Visual Studio licence?
You could try to use NUnit or other unit test frameworks. There are a lot of frameworks free of charge that can be used.
Below you can find script that extracts the assemblies needed by MSTest if you are using Visual Studio 2013. The script is written using the example written by Wim Coenen for VS2010 (I updated them for VS2013).
The only thing that is missing is the command to extract the registry information needed by MSTest.
@echo off
setlocal
set here=%~dp0

mkdir mstest
set targetfolder=%here%mstest

set programs=%programfiles%
if exist "%programfiles(x86)%" set programs=%programfiles(x86)%
set vs2013="%programs%\Microsoft Visual Studio 12.0"
set gac2="%windir%"\Microsoft.NET\assembly
set gac1="%windir%"\assembly

echo === Copying from Visual Studio 2013 install folder...
copy %vs2013%\Common7\IDE\mstest* "%targetfolder%"
copy %vs2013%\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.Quality* "%targetfolder%"

echo === Copying from %gac1%...
pushd "%gac1%"
dir /s /b *.dll | findstr QualityTools | findstr 12.0.0.0 > %here%tmp.filelist
popd
for /F "tokens=*" %%f in (tmp.filelist) DO copy "%%f" "%targetfolder%"

echo === Copying from %gac2%...
pushd "%gac2%"
dir /s /b *.dll | findstr QualityTools | findstr 12.0.0.0 > %here%tmp.filelist
popd
for /F "tokens=*" %%f in (tmp.filelist) DO copy "%%f" "%targetfolder%"

del tmp.filelist

echo === Done. Check output for errors!
exit /b 0

Comments

  1. It should be possible to install MSTest on a server by installing just the test agent (http://www.microsoft.com/en-us/download/details.aspx?id=38186 ) but I'm not sure about the licensing part..

    ReplyDelete
    Replies
    1. In our case we don't talk about servers. My case was simple users that wanted to run some unit test on their local machines to validate different things.

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too