Visual Studio Test Explorer window will not open

unit-testing visual-studio-2012 visual-studio-2015 dotcover test-explorer
WheretheresaWill picture WheretheresaWill · Jul 12, 2013 · Viewed 49.1k times · Source

For some reason I can't open the test explorer window in Visual Studio 2012. I click Test->Windows->Test Explorer and nothing happens...

This problem may have been caused by recently uninstalling DotCover. I did this because my licence expired and I was having issues running tests without it (context menus weren't working).

Any suggestions or advice much appreciated!

Thanks.

Answer

Edward Brey picture Edward Brey · Oct 25, 2013

In VS2012, Test Explorer has a bug in that the window doesn't get focus when you click Test > Windows > Test Explorer. Instead, the menu item has no effect unless the window was complete hidden, in which case it is displayed.

The bug means that if Test Explorer is collapsed with Auto Hide, the menu item does nothing. Check that Test Explorer isn't in an auto-hide tab somewhere off to the left or right (i.e. in a tab with text written vertically, like Server Explorer and Toolbox are by default).

Update: The bug is fixed in VS2013.

Related questions

Tests not running in Test Explorer

I am currently working on a solution that has currently 32 Unittests. I have been working with the resharper test runner - which works fine. All tests are running, all tests are showing the right test outcome. However, the tests are …

Read More
Where is the "Create Unit Tests" selection?

I have installed the new Visual Studio 2012 Ultimate. I have created a Test Project with my solution and it contains some default unit tests. However right clicking on new Methods doesn't show the "Create Unit Tests" context menu any longer. …

Read More
Why is the xUnit Runner not finding my tests

I have a xUnit.net Test as follows: static class MyTestClass { [Fact] static void MyTestMethod() { } } The xUnit plugin for VS 2012 says: No tests found to run. TestDriven.net runs it fine but mentions something about Ad hoc: 1 passed, 0 failed, 0 skipped (…

Read More