I get that MTM test configurations are for tracking and management purposes but in order for them to be useful and model actual tests we need a way to get them into visual studio test methods as parameter values.

For example with CodedUI Cross Browser testing we need to assign the browser type. Yet if I need to execute the test against three browsers IE/FireFox/Chrome the only recommended way to do this (without duplicating code) is through a data source. The problem with data sources is that the test will iterate through all possible browser values (performing three tests) and results will then appear as coming from one test case. So the MTM test configuration is meaningless on it unless i have one configuration value of "IE/FireFox/Chrome" which isn't very useful if i want to filter test results by configuration (which is the point of MTM configurations).

I currently have a unit test that fails only when another particular test runs first. The problem is that I have no idea what order my unit tests are running in so I have no way of knowing WHICH test is causing the subsequent failure. If I could sort by last run date, I would know which test ran before the failing test and that would be all I needed.

I tried running my tests through the VSTest.Console.exe to create a trx file so I could see the history, but the console app runs the test in a particular order that does not cause the error. The Test Explorer appears to run tests in a semi-random order, which always causes the error.

I currently have 284 tests that COULD be causing the problem, but have no way of tracking down which one it is. Please help!

It would be really useful to be able to import arbitrary timing data into VS Load Test and display them as part of the counter tree, so that we can:

1) Import Perfmon binary or text files from machines which cannot be monitored or logged on to from inside the test environment, for example web service machines which exist at third-party sites or in a different domain.

2) Import timings from non-Windows systems, such as network hardware, UNIX, BSD and Linux servers.

3) Create and import custom counters from databases (in our case, BizTalk business process timings from the BAM database)

See this thread for discussion:
http://social.msdn.microsoft.com/Forums/en-US/vstswebtest/thread/e31fc208-e62c-4f48-9de8-96c5b6d57e11/

The new Unit Test Explorer seems great, but would be even nicer if we can just run Unit Tests by selecting Unit Tests from the Solution Explorer. For example:

- Right click on a Unit Test within solution explorer and select for example "Run Unit Test" on the Context menu.

- Right click on the whole Unit Test class within solution explorer and select for example "Run Unit Tests" on the Context menu.

- Right click on the whole Unit Test project within solution explorer and select for example "Run Unit Tests" on the Context menu.

I think some third party tools does this upto some extent, but it would be nice feature to have in the next VS.
This will make dev work more seamless. The result can be published in the Unit Test Explorer as usual.

Currently the Code Coverage details that are loaded into the TFS warehouse use a naming scheme that is not well documented. Nor is there an existing API that can be used to convert from other 'popular' naming schemes or API's to the format Code Coverage uses.

For my TFS Warehouse extension I want to integrate into the existing DimCodeElement dimension, which is fed using the above mentioned formatting for Types and Members. In order to reference the correct CodeElement I need to generate the same strings inside my WarehouseAdapter.

Microsoft,

A) Please provide a public PersistenceNameProvider, akin to the existing NameProviders in Microsoft.CodeAnalaysis that we can use to convert from a Microsoft.Cci INode or a System.Reflection based ITypeInfo/IMemberInfo.

Or alternatively create a cross tool naming format which will be used inside the warehouse.

See also:
internal abstract class PersistenceNameProvider : NameProvider
Name: Microsoft.FxCop.Sdk.NameProviders.PersistenceNameProvider
Assembly: Microsoft.VisualStudio.CodeAnalysis, Version=10.0.0.0

Or

B) Provide detailed documentation on the formatting used for the different languages supported by CodeCoverage (C#, VB.NET, F#, C++). That way we can implement something like this ourselves.

-- SUBMITTED BY AN ALM RANGER.

A serious usability problem of Test Manager is the separation of activities between different clients:

1) Not having the possibility of managing Test Steps in Team Explorer and Web Access is a big problem, and I have already voted some suggestions which asked for this.

but, more in general:

2) We do not want different clients to manage <testing> and <the rest of the project>: we suggest having all the functionalities (so including plan/suite/results/lab/etc. management) directly from Team Explorer and Web Access clients.

Background:
- we have agile teams, where PO, testers and developers collaborate closely.
- during an iteration planning meeting, User Stories acceptance criteria are finalized, and basic Test Cases (Acceptance Tests) are drafted.
- The collaboration between testers, developers and PO continues during the iteration, when US are better analyzed (and so also Test Steps are refined), always in the same collaboration manner.

Having to switch from a client to another one to manage and also retrieve data is a big impediment to collaboration.

Thank you very much!