Wednesday, March 21, 2012 7:40 PM
I have some tests that are failing only when all of my unit tests are run. I'd like to select all of the unit tests in the test assembly and debug them. I see a Run All option, but no Debug All option.
The interface seemed awkward because I couldn't "show all" passed and failed tests. I finally got around this by running the failed tests to watch them all pass. Once they all were listed as "passed", I could select them all and then run Debug selected unit tests.
The new Unit Test explorer feels "dumbed down" from the previous version of Visual Studio. It's great for basic tasks. It feels restricting. I miss seeing test details (for passed tests) and copying test output/results.
Sunday, March 25, 2012 9:11 AM
I am completely agree, see this post:We are volunteers, if the reply help you mark it as your answer. thanks!!
Monday, March 26, 2012 9:19 PM
We have done a bunch of work in this area since the Beta timeframe based on similar feedback from other customers.
Seeing all your tests is now the default. Running and debugging specific groups or filters of tests is easier. And a lot more.
BTW, you can right-click copy a test in the Beta, but we are working to add a better experience for that.
-- Peter Provost Sr. Program Manager Visual Studio ALM Microsoft Corporation
- Proposed As Answer by Todd KingMicrosoft Employee Wednesday, October 10, 2012 2:07 AM