There are few different ways by which you can make your extension visible to test explorer in Visual Studio 11. Let us go through them one by one.
1. Drop it in “Extensions” folder
This is the most simplest way to make the extension visible and it works for all the 3 well known clients (VS, command-line, team build). The exact steps are as follows: -
2. Install the VSIX provided by the extension provider
This is another simple way to make the extensions visible and it works for almost all the scenarios. The only place where it does not work is with a 64 bit team build system. The exact steps are as follows: -
3. Check-in the extension in the version control
This makes the extension visible only for team build machine and is not applicable for VS and command-line clients. The exact steps are as flows: -
4. Use Nu-get extensions (Updated 29/8)
As Tejre mentioned here, you can also make your extensions visible via Nuget packages. This support was not available in Visual Studio 11 and got added in an update and it works for all the 3 clients (VS, command-line, team build). The exact steps for VS/team build are: -
For command-line, you should specify /TestAdapterPath switch to pass on nuget adapter location. Example: -
vstest.console /TestAdapterPath:"C:\Users\aseemb\Desktop\UnitTestProject1\packages" "C:\Users\aseemb\Desktop\UnitTestProject1\UnitTestProject1\bin\Debug\UnitTestProject1.dll"