Comments on: Visual Studio 2005: Still wondering where the unit-testing tools are http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/ Life, .NET, and Cats Fri, 21 Nov 2008 04:07:45 +0000 http://wordpress.org/?v=2.5 By: Not a Muppet http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5467 Not a Muppet Sat, 11 Aug 2007 13:42:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5467 What a poorly-researched and knee-jerk rant! <br> <br>My team is happily running VSTS unit tests from our automated command-line MSBuild, without a GUI, including getting full code coverage information out. <br> <br>It's really not very hard to discover the mstest.exe command-line, and this is available in the Developer Edition. <br> <br>We did end up writing a (small) MSBuild task to get the coverage out as XML in the format we wanted, but all the APIs are clearly there to allow you to do this however you want. And we only had to do this because we couldn't move to the TFS server because we couldn't switch away from our existing SCM system. <br> <br>It's not without its faults but it doesn't deserve the lazyily-researched invective you pour out in this article. <br> <br> What a poorly-researched and knee-jerk rant!

My team is happily running VSTS unit tests from our automated command-line MSBuild, without a GUI, including getting full code coverage information out.

It’s really not very hard to discover the mstest.exe command-line, and this is available in the Developer Edition.

We did end up writing a (small) MSBuild task to get the coverage out as XML in the format we wanted, but all the APIs are clearly there to allow you to do this however you want. And we only had to do this because we couldn’t move to the TFS server because we couldn’t switch away from our existing SCM system.

It’s not without its faults but it doesn’t deserve the lazyily-researched invective you pour out in this article.

]]> By: Joe White's Blog http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5469 Joe White's Blog Mon, 05 Feb 2007 12:09:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5469 <strong>ReSharper, day 5: Integrated unit-test runner</strong> ReSharper, day 5: Integrated unit-test runner

]]> By: Mensur http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5466 Mensur Fri, 26 Jan 2007 21:20:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5466 You can set your test project as a startup project and the just hit Run and all tests will be run. You can set your test project as a startup project and the just hit Run and all tests will be run.

]]> By: Joe White http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5465 Joe White Wed, 14 Jun 2006 11:50:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5465 Sure, it's possible to manually run selected tests. What's painful is running ALL the tests. You have to manually open up that window, and manually check every test, every time you open Visual Studio. Pretty cumbersome and error-prone for something you do dozens of times a day. Sure, it’s possible to manually run selected tests. What’s painful is running ALL the tests. You have to manually open up that window, and manually check every test, every time you open Visual Studio. Pretty cumbersome and error-prone for something you do dozens of times a day.

]]> By: Ming http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5464 Ming Tue, 13 Jun 2006 18:58:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5464 Hi, <br> <br>On the Test toolbar there is button called 'Test View' it shows you all the tests in another little window. You can then right click and select all and then do a Run selected to run all the tests. <br> <br>I'm kinda new but this might be something you already know. <br> <br>Ming Hi,

On the Test toolbar there is button called ‘Test View’ it shows you all the tests in another little window. You can then right click and select all and then do a Run selected to run all the tests.

I’m kinda new but this might be something you already know.

Ming

]]> By: Joe White's Blog http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5468 Joe White's Blog Tue, 06 Jun 2006 23:38:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5468 <strong>Running all the unit tests from Visual Studio</strong> Running all the unit tests from Visual Studio

]]> By: PeteM http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5463 PeteM Sun, 26 Feb 2006 22:26:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5463 This article looks like it could hold a lot of answers re VSTS unit tests, MSTest.exe, etc: <br><a target="_new" href="http://msdn.microsoft.com/msdnmag/issues/06/03/Bugslayer/default.aspx" rel="nofollow">http://msdn.microsoft.com/msdnmag/issues/06/03/Bugslayer/default.aspx</a> <br> <br>Cheers, <br>Pete. This article looks like it could hold a lot of answers re VSTS unit tests, MSTest.exe, etc:

http://msdn.microsoft.com/msdnmag/issues/06/03/Bugslayer/default.aspx

Cheers,

Pete.

]]> By: anonymous http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5462 anonymous Thu, 09 Feb 2006 21:00:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5462 try MSTEST.exe <br> <br><a target="_new" href="http://msdn2.microsoft.com/en-us/library/ms182489.aspx" rel="nofollow">http://msdn2.microsoft.com/en-us/library/ms182489.aspx</a> <br> <br>I'm not sure which edition MSTEST comes with. <br>Maybe you need to buy a "testers edition"? <br> <br> try MSTEST.exe

http://msdn2.microsoft.com/en-us/library/ms182489.aspx

I’m not sure which edition MSTEST comes with.

Maybe you need to buy a "testers edition"?

]]> By: Jeff Atwood http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5461 Jeff Atwood Fri, 20 Jan 2006 21:18:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5461 > The most fundamental operation for unit tests is running all the tests. That's the point. Yes, it can be useful to run a subset of the tests, but that's a feature you add later. The first thing you write in any testing framework is "Run All Tests". Because it's something you do dozens of times a day. You do it all the time, because every time you change your code, you want to know you didn't just break something. If you're only running a single test after each change, and you get to the end of the day and find out you broke some other test, you have no idea when you broke it. Which is why you don't run a single test. You run all the tests, unless you have a really good reason not to. <br> <br>I think this might be because they're really targeting TESTERS-- let's say offshore testers-- rather than developers with this feature. <br> <br>Definitely a legitimate criticism, but I wonder if the focus is a little different than something like NUnit. > The most fundamental operation for unit tests is running all the tests. That’s the point. Yes, it can be useful to run a subset of the tests, but that’s a feature you add later. The first thing you write in any testing framework is "Run All Tests". Because it’s something you do dozens of times a day. You do it all the time, because every time you change your code, you want to know you didn’t just break something. If you’re only running a single test after each change, and you get to the end of the day and find out you broke some other test, you have no idea when you broke it. Which is why you don’t run a single test. You run all the tests, unless you have a really good reason not to.

I think this might be because they’re really targeting TESTERS– let’s say offshore testers– rather than developers with this feature.

Definitely a legitimate criticism, but I wonder if the focus is a little different than something like NUnit.

]]> By: Matt http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5460 Matt Tue, 17 Jan 2006 22:04:00 +0000 http://blog.excastle.com/2006/01/14/visual-studio-2005-still-wondering-where-the-unit-testing-tools-are/#comment-5460 Do you think perhaps Microsoft doesn't know these basic facts about Unit Tests, becuase they don't perform Unit Tests themselves? :) Do you think perhaps Microsoft doesn’t know these basic facts about Unit Tests, becuase they don’t perform Unit Tests themselves? :)

]]>