visual-studio-test-runner

I am trying to implement a custom Test Adapter, all the files are bellow: TSTestDiscoverer.cs TSTestExecutor.cs TSTestContainer.cs TSTestContainerDiscoverer.cs VsSolutionHelper.cs from XMLTestDiscoverer source code Using vstest.console.exe /listdiscoverers /usevsixextensions:true I confirmed that the extension is installed and it is listed on the test discoverers. Running vstest.console.exe file.ts I confirmed that both TSTestDiscoverer and TSTestExecutor are working correctly. Now I want to list the tests on Test Explorer, for that I guess I need ITestContainer and ITestContainerDiscoverer .

Recently I came to know about the nuget based adapter/runner ( http://xunit.github.io/docs/running-tests-in-vs.html ) I was trying to understand how these runners/adapters are recognized by Visual Studio and then used by the TestWindow. For example, if I install "xunit.runner.visualstudio" nuget package all the xUnit based tests in my project are discovered and displayed in the Test Window. I am trying to understand how does VS hook the Test Discovery using the package installed in packages folder? Where/how do VS and nuget based adapter get hooked? I tried finding this information but my

I've got a fairly small C# solution with about 5 projects in it. I am using Visual Studio 2012 with Update 4, and Resharper 8.1 (build 8.1.23.546). It's on an I7 with an SSD and 16GB RAM, with oodles of disk space. Performance on this machine is fantastic for everything else. I have R# set to be my unit test runner, and I've noticed that as soon as I run any unit tests (one or many, pass or fail, makes no difference), the Visual Studio text editor becomes almost unusable. Typing into the editor window suffers such extreme lag (up to 1 second between keystrokes) that it completely breaks down

When I open Visual Studio 2013 and load my solution I'm greeted by an error message telling me the Test Window is unable to load. The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information. 1) Cannot compose part 'Microsoft.VisualStudio.TestWindow.Controller.TestsServiceInternal' because a cycle exists in the dependencies between the exports being composed. To break this cycle, consider changing some imports from constructor to property injection. Element: Microsoft.VisualStudio.TestWindow