103 votes19 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald HofmanAnonymous commented
I'd like this for the reasons below, but also because I want to answer the question 'how many hours work did I have assigned at the start of the sprint'.
730 votesAnonymous commented
#36: No appreciable hierarchy (like the Resharper test runner). Our standard is to have <className>Tests as the name of the testing class for class name. Each one has a standard test method 'CanConstruct' to ensure the constructor doesn't throw. Simple enough. View that in the Test Explorer and you're presented with a monolithic list of items with no way to differentiate between them without going and adding attributes. Add a tree view - assembly - namespace - class - test. Lack of this prevents me using the VS test stuff.