For PTVS we use helper classes for interacting with Visual Studio.

We should port the core pieces of this functionality into VSTestHost so that people do not need to reimplement it themselves.

Whenever you launch Visual Studio in a new hive, you get this screen:

Is there any way for an integration test to skip this or otherwise automate pressing the "Not now, maybe later" link? It's been a bit of a pain to have to do this on every new machine your tests run on. Perhaps VisualStudio-TestHost should even do this by default?

Why is this package installed in the IDE installation's PrivateAssemblies folder rather than in the user's AppData folder where other VSIX packages get installed?

Visual Studio 2015 may throw Microsoft.VisualStudio.ExtensibilityHosting.InvalidMEFCacheException if the cache is invalid and needs to be regenerated.

We should handle this exception in the test adapter, restart VS and retry the test.

I would like to know if possible how I can use this tool to perform some integration testing for a visual studio extension. I will need to write end to end tests from the time a user starts interacting with the visual studio extension, including UI tests. I have checked for any documentation online with no success.

Currently we load VS settings from the run settings (*.testsettings file), but properties can also be applied to individual tests:

[TestMethod]
[TestProperty("VSVersion", "12.0")]
[HostType("VSTestHost")]

We should add the logic required to re-evaluate the required VS instance for each test based on the test properties, restarting the instance if necessary.

I don't think it's possible to re-order tests to group ones with matching properties, so having lots of different tests in the same class may not be a good idea for performance, but for small projects it'll be more convenient than dealing with multiple separate files.

Can you create a gitter.im room for this repository by any chance, similar to what the roslyn/corefx/coreclr teams have done?

This version of SQL Server Management Studio:
https://msdn.microsoft.com/en-us/library/mt238290.aspx

If you have VS Test Host Adapter 1.0.4 installed, you'll get this on startup:

---------------------------
Microsoft SQL Server Management Studio
---------------------------
The 'VSTestHostPackage' package did not load correctly.



The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\huvalo\AppData\Roaming\Microsoft\AppEnv\14.0\ActivityLog.xml'.



Restarting Visual Studio could help resolve this issue.



Continue to show this error message?
---------------------------
Yes   No   
---------------------------

From activity log:

  <entry>
    <record>55</record>
    <time>2016/10/27 21:21:23.855</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
    <guid>{4A7E4285-12F6-4CEB-B878-F029A43A5315}</guid>
  </entry>
  <entry>
    <record>56</record>
    <time>2016/10/27 21:21:23.855</time>
    <type>Warning</type>
    <source>VisualStudio</source>
    <description>Appid denied the loading of package</description>
    <guid>{4A7E4285-12F6-4CEB-B878-F029A43A5315}</guid>
  </entry>

When I try to run the simple tests of the attached solution, I always get:

The test adapter ('Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestAdapter, Microsoft.VisualStudio.QualityTools.Tips.UnitTest.Adapter, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') required to execute this test could not be loaded.

UnitTestProject2.zip

My VS version is:

I'm experiencing the issue described in Issue #36 (now closed). After following the patch instructions on that issue, I get the following test result output (VS is never launched):

TestContext Messages: Launching VisualStudio: "...\Microsoft Visual Studio 15.0\Common7\IDE\devenv.exe" Failed to launch devenv.exe (VisualStudio, 15.0) Restarting VS Launching VisualStudio: "...\Microsoft Visual Studio 15.0\Common7\IDE\devenv.exe" Failed to launch devenv.exe (VisualStudio, 15.0)

I have carefully followed the instructions to create the symbolic links and am using the right .testsettings file, but I am still seeing this as the result of my test runs (tried my own project and the example at the start of this issue):

Anyone have any ideas for what I can try / where I can look?

After upgrading from v1.0.1 to 1.0.2:

• With VS2013 everything is fine
• With VS2015: our solution builds OK, tests are OK but VS display intellisense errors:

CS0234 The type or namespace name 'VSTestHost' does not exist in the namespace 'Microsoft.VisualStudioTools' (are you missing an assembly reference?)

Perhaps a Roslyn bug ?

Hello, I just tried to use this extension but within Unittest-files I only get the following errors:

Severity Code Description Project File Line Suppression State Error CS0246 The type or namespace name 'HostTypeAttribute' could not be found (are you missing a using directive or an assembly reference?) UnitTestProject5 C:\temp\UnitTestProject5\UnitTestProject5\UnitTest1.cs 10 Active Error CS0246 The type or namespace name 'HostType' could not be found (are you missing a using directive or an assembly reference?) UnitTestProject5 C:\temp\UnitTestProject5\UnitTestProject5\UnitTest1.cs 10 Active

Have a look on the screenshot.
Within PowerShell not install error occur.
The testsettings files are provided VS' install directory, the dlls are there as well.

But in VS the HostType is unknown.

What should I do?

Looks installed:

Automatically capture the screens of the test machine so when errors occur on headless devices we can see what was happening.

Bonus points to only keep images that changed from the previous one, to only keep images from failed tests, and/or to use some form of delta compression between frames.

What is the recommended practice for testing an extension in Visual Studio 2010 or 2012, using Visual Studio 2013 or 2015 to launch the tests? I'm looking for guidance regarding automation of the following items:

1. Deploying the extension to the correct version of Visual Studio
2. Selecting the .testsettings file which matches that environment
3. Running tests outside the debugger
4. Running tests in the debugger