It will be a better feature to choose a different UIMap when you create a coded UI test from an existing recording or Test and Lab manager. Currently, you have to edit the UIMap to move some code in another UIMap and it's not very funny !

When test plan is defined it would be nice to have ability to order test suites in it as you can order test case in test suite (ability to edit SequenceNumber from table tbl_SuiteEntry for suites)

Currently it is very unpredictable which monitor will be recorded when using the video recording feature. It is very easy to record sensitive information such as the testers personal email.

By default it should only record the monitor that test runner is on but this should be configurable incase testers use a different monitor for the Application Under Test

Ideally it should be more obvious which monitor is being recorded. A slight red glow around the monitor in question when recording would be nice.

When Assinging a build to a plan (Track - Assing build or recommend tests)
You get a list of associated work item (if the team is associating WI to changesets)

It would usefull to see the parent work item in the list as often we are more interested in the associated ser story or PBI.

Seriously, how can you not support web technology on iPad and the fastest growing browser out there? Supporting Chrome and Safari is a requirement for many companies in the web development business and not having that with VS2012 is a massive drawback.

The feature pack 2 and the support for the Firefox was a great advance, however the Firefox has been updated and the adoption of Chrome is increasing and all the time that I show MTM for my customers, the first question is "Do you support Chrome and Firefox?".

It's unnecessary say that, sometimes it is a blocker.

Define a new test attribute or extend the TestMethod/TestClass with a property to indicate the the particular test method or all the test methods in the test class can run in parallel we the other, because the are completely thread safe; in this way is possible to use all core to run more efficiently the tests.

Add support for monitoring UNIX server resources in load tests. Perhaps pull counters from NMON similar to how perfmon is accessed in Windows

In Native Unit Tests, a TEST_METHOD can be grouped under a TEST_CLASS and the same is reflected in the Test Explorer.

In a similar fashion, I would like to group BOOST_AUTO_TEST_CASE under BOOST_AUTO_TEST_SUITE and same be reflected in the Test Explorer.

Example Code:

BOOST_AUTO_TEST_SUITE( test_suite1 )

BOOST_AUTO_TEST_CASE( test_case1 ){ BOOST_ERROR( "some error 1" ); }

BOOST_AUTO_TEST_CASE( test_case2 ){ BOOST_ERROR( "some error 2" ); }

BOOST_AUTO_TEST_SUITE_END()

In the above example, two Test Cases belong to a common Test Suite.
Hence i would like these two test cases be grouped under this Test Suite and reflected in the Test Explorer Window.

When unit tests are being run, very little feedback is given in Test Explorer. It is very hard to know that something is going on.
The test icon changes only after each test is executed. If the icon of the test reflected its "pending" state, it would be helpful.

Currenlty if a assert fails, the test stops
(Since the CodedUI is built on top the unit test framework)

But in a Coded UI test you may have multiple assert in a page and currently you have code a Try Catch block.
In web performance test the continue on error does exist.

(the feature pack 2 as misleading Continue on Error but that is only associated to playback)

As a product owner I want to review PBIs and related Test Cases, including test results, in TFS so that I know what to review for product readiness. I do not appear to be able to perform this simple function if we use Test Manager.

currently only VM running on Hyper-V are directly supported.

All other virtualization solution requires treating the VM like physical machine and therefore it is not easily possible to test a multiple machine setup. Especially ESX based virtualization is very common.

Could a delta of the VHD (virtual hard disk) be created when deploying the virtual machine in the Lab Management tool instead of creating a full copy of the VHD? This would do two things: 1) greatly speed up the time that it takes to deploy the virtual environments 2) reduce the amount of SAN storage that is needed to support Lab Management.

Add spell check functionality to MTM so that test case writers have the ability to spell check test case steps etc.