Suggestion:
Add ability to allow using list of Data Providers for unit test.
If two or more Data Providers connected to unit test then unit test uses multiplication of this data.

Example:
[TestMethod]
[DataSource("System.Data.SqlClient", "Data Source=<MyDB>;Initial Catalog=TestDB;Integrated Security=True", "Projects", DataAccessMethod.Sequential)]
[DataSource("System.Data.SqlClient", "Data Source=<MyDB>;Initial Catalog=TestDB;Integrated Security=True", "Operators", DataAccessMethod.Sequential)]
public void MyTest1()
{
Projects Project = ConvertToProject(TestContext["Projects"]);
Operators Operator = ConvertToOperator(TestContext["Operators"]);
Assert.IsTrue(SomeAction(Project, Operator))
}

For data in tables
Projects
| Id | Setting | Status |
| 1 | 1 | 1 |
| 2 | 1 | 2 |
| 3 | 2 | 1 |
Operators
| Id | Locale | region |
| 1 | ru-RU | 1 |
| 2 | en-EN | |

This unit test will be executed 6 times

This is really neccessary feature for us and while we haven't this in VS Studio we need to use some our workarounds... But this is not good. (e.g. for testing some reports for projects connected to some operators I need to have tables Projects and Operators in DB this is like application works)

In most cases we in any case creating test data in DB not only for using it in comparing data in Unit test but for application work and this will be very good to use this ata from DB and do unit test for all possible variants

Thanks

You claim to have completed the suggestion to sort test cases - but you haven't. Really. Currently, to make test explorer usable, I have to (manually) enforce two naming convention rules:

1) Every test CLASS must be uniquely named within the entire SOLUTION.

2) Every test CASE must be uniquely named within the test ASSEMBLY.

Both of these are troublesome and problematic. And both would be fixed if you would:

A) In the 'Group by Assembly' view, test cases should be sub-grouped by their class.

B) In the 'Group by Class' view, test case group names should be the fully qualified class name - not just the short name. (This would apply to the class sub-groups above as well.)

Every test system I've used prior to this used namespaces to group test classes - and the 2012 Test Explorer is the only one that IGNORES THEM.

I've seen people talking about a few hundred, or even a few thousand test cases. I've got 150 projects in my solution - and another 150 unit test projects. Each unit test project has between 2,000 and 10,000 test cases. The 'flat' two-dimensional test sorting is very painful to use.

In both Visual Studio and Test Manager you can perform searches using non specific dates. i.e. activated date < @today-1. This is a very useful feature.

At the moment when using parameters within Test Manager you have to specify an exact date (i.e. 01/01/2012). This is fine when you only intend to run a test case once but when the test case is repeatable the date in the parameter may need to constantly need to be changed when the test is reused.

It would be great if you could specify non specific dates within the parameters so that the date was always generated in test runner.

i.e.
Action: Enter a date of @Today+1
Expected Result: results returned will be equal to the date entered
Parameter: Will always equal tomorrows date and will NEVER need to be respecified in order to run the test.

When alt-tabbing away from Test Manager so I can check the steps I am writing against the target app, cursor position is reset to the first space of the currently highlighted field when returning to Test Manager.

This applies any time Test Manager loses focus to another application, whether the user alt-tabs, selects another app from the taskbar, etc.

Steps to repro:
1. Open Microsoft Test Manager and open an existing test suite, or create a new one
2. From the Plan tab, click New in the Test Suite view (right pane) to create a new test case (or open an existing test case)
3. Begin typing in any field. Note that the cursor position is left at the end of the current string of text. Select ALT-TAB to switch to a new window.
4. Select ALT-TAB to return to Test Manager. Note that the cursor position has reset to the beginning of the current string of text.

Expected Results:
Cursor position is maintained regardless of user action, as seen in other MS apps.