Include Pex and Moles with all editions of Visual Studio including Professional edition rather than being restricted to developers with Premium or Ultimate editions of Visual Studio. This will allow all Visual Studio developers to leverage the capabilities of the Moles mocking library and the additional feedback for Unit Testing available with Pex.

In Visual Studio 2015 IntelliTest are a fantastic idea!
Restricting it to Visual Studio Ultimate is not a good news. Please make it available to more users.

When running tests in Test Explorer, there doesn't appear to be a way to export these results. This would be useful in order to share failed test results with fellow team members. Ability to export to trx would be wonderful. I know this can be accomplished via commandline, but running from commandline is a rather clunky solution, especially if you want to re-run failed test.

Please extend IntelliTest to enable generating tests for VB.NET projects.

Spec Explorer 2010, a model-based testing tool extension is supported in Visual Studio 2010/2012, this suggestion is to make it work with Visual Studio 2013.

We have over 200 projects, 2900+ unit tests. It takes over a minute some times to get to the point where it can start listing all the unit tests in the test window, and start executing. We have latest gen Core I7, 8GB 64 bit windows, and it is still a pain. Maybe this area needs 're-imagining', as I can understand the complexities of managing this large number of projects/tests, but it is not working well for us.

Action Recordings (https://msdn.microsoft.com/en-us/library/dd286647(v=vs.110).aspx) are nearly useless and are very fragile. Instead Xamarin Test Recorder https://www.xamarin.com/test-cloud/recorder should be integrated into MTM (Microsoft Test Manager) and extended to work with WPF/Win Form/ Desktop applications that require automated testing.

Microsoft Fakes is powerful function for testing. Please provide support to use Microsoft Fakes Stub/Shim context in .NET Core test project.

This entry tracks the interest in seeing the VS Test Explorer open sourced.

I am working on solution that contains 13 000+ unit tests split between several (10+) projects. I am trying to use TDD, but after each build there is a long time window while Test Explorer tries to discover ALL the tests in my solution.
I need an option to disable/enable the automatic test discovery and a new command to trigger it manually whenever I need to refresh the test list. This will save me literally hours each day.

Include assertion checks in the HTML log file created by QTAgent this is essential for testers as many times they are asked to show proof specially in medical companies(at list that what my personal experience says)

Please enable code coverage support for Windows Phone projects.

Please enable code coverage support for Windows Store Applications (Windows 8 Apps).

Enable ordered test support for MSTest V2 framework based tests.

Spec Explorer is a masterpiece for testing requirements:
It is closest to the best general known way of defining requirements ( thanks to abstract state machines) in a language you master using a very rich object-object oriented architecture!
Please make it work with Visual Studio 2015.

Please extend IntelliTest to generate tests for .NET Core projects.

Enable IntelliTest for 64 bit projects

It's great to see some of the previously Ultimate-only features such as CodeLens moving downlevel to the Professional edition, so thanks! It's maybe too late to do this for RTM, but please consider also including the Code Coverage Analysis tool in the Professional edition of VS 2015 rather than limiting it to Enterprise.

Performing code coverage analysis is an integral part of any unit testing workflow, but it's hard to justify the cost of Enterprise for just this one built-in feature when something like JetBrains dotCover can just be purchased separately.