Pondering TDD in Microsoft .NET, Second Edition

re: Pondering TDD in Microsoft .NET, Second Edition

todd brooks — Thu, 07 Sep 2006 07:28:45 GMT

I would think that VSTS might prove to be better fodder for writing, since the documentation (or lack thereof) leaves much to be desired. OTH, not everyone can afford VSTS and that would segment your market appeal.

Much has been written about NUnit, so I'm not sure if there is new ground to cover. With VSTS and the inclusion of MS Build Server with Team Foundation Server and the ability to run unit tests with the automated builds, it sounds like there is a lot of new tech to cover. Not much has changed with regards to TDD, so you will mainly be updating on best policies and procedures and the inclusion of how's and todo's when using the different tools. And like I said, the MS docs leave much to be desired...especially with regards to Team Foundation Server and the automated builds with unit testing.

Intersting Finds: September 7, 2006

Jason Haley — Fri, 08 Sep 2006 05:23:03 GMT

re: Pondering TDD in Microsoft .NET, Second Edition

Kevin Dente — Fri, 08 Sep 2006 06:13:01 GMT

I vote NUnit. It's something of a defacto standard (even such that many other frameworks support NUnit attributes). It's free, thus the barrier to entry is low (it can work against VStudio Express, not requiring a special-edition IDE).

On the other hand, including a chapter on working with other tools would be nice.

re: Pondering TDD in Microsoft .NET, Second Edition

cs — Fri, 08 Sep 2006 07:37:06 GMT

Update the nunit stuff where it makes sense. Use MbUnit when it has a feature that is very useful. I'd prefer to have VSTS left out since it costs too much for the average developer.

re: Pondering TDD in Microsoft .NET, Second Edition

leaffere — Fri, 08 Sep 2006 11:17:44 GMT

I vote nUnit. Not alot of people have made the monetary leap to Team System.

Some TDD Links

Dan's Archive — Fri, 08 Sep 2006 17:05:49 GMT

re: Pondering TDD in Microsoft .NET, Second Edition

Jason Haley — Fri, 08 Sep 2006 17:51:58 GMT

I vote for NUnit too ... and I would also like to add that if you write it - I'll buy it.

re: Pondering TDD in Microsoft .NET, Second Edition

Nathan — Sat, 09 Sep 2006 04:58:51 GMT

mbUnit. While nUnit seems content to sit around with its basic unit testing ability, mbUnit keeps adding new, spiffy features.

Interesting Finds: September 7, 2006

Jason Haley — Sat, 09 Sep 2006 05:51:28 GMT

re: Pondering TDD in Microsoft .NET, Second Edition

brucenan999 — Tue, 12 Sep 2006 04:40:35 GMT

FREE tools are best choices. NUNIT, NFORMUNIT, NDBUNIT,NASPNET are good tools for .net unit test.
I think you can extend the NUnit to test other sides such as Win Form, Database, ASP.Net, Windows Service and so on.

re: Pondering TDD in Microsoft .NET, Second Edition

Morten — Tue, 12 Sep 2006 20:44:35 GMT

I definetly vote for VSTS! A great deal of the .Net developers have an MSDN subscription, and my understanding is that the vast majority of the ones who don't have such a subscription will not read your book anyway, because TDD is so far away from their hobby, leisure, amateur programming realm that they wouldn't know how to use it.

Morten

re: Pondering TDD in Microsoft .NET, Second Edition

Scott Bellware — Fri, 15 Sep 2006 03:28:24 GMT

Since TDD in Microsoft .NET was released a few cool things have begun to unfold in the TDD world. BDD being one of them. I hope you'll give some time to nSpec tools due to the approaches they engender.

I think NUnit is a better choice for xUnit tool to focus on the book because of its user base. I also agree that the other frameworks should be touched on - at least for those features that are inventive and interesting.

re: Pondering TDD in Microsoft .NET, Second Edition

corbinhoenes — Wed, 20 Sep 2006 06:50:43 GMT

NUnit is the better choice. It get's the job done and it's availabe to everyone.because everyone. Touching on other tools (MbUnit / VSTS) and their advanced usages is a great idea.

Honestly I have no clue what advantages VSTS has--so learning about them would be nice. We worked briefly with MbUnit because it was a superset of NUnit but realized that 90% of our unit testing was just using plain old NUnit features so we switched back.

re: Pondering TDD in Microsoft .NET, Second Edition

Mark C — Wed, 04 Oct 2006 01:04:32 GMT

I vote MbUnit. It has a lot of great features but is losing the publicity war with NUnit.

A look ahead at 2008

Andrew Stopford's Weblog — Thu, 27 Dec 2007 21:50:55 GMT

It's that time of year again and a custom on my blog to look back at my predictions for this year, relect

James Newkirk s Blog Pondering TDD in Microsoft NET Second Edition | Insomnia Cure

Tue, 09 Jun 2009 01:00:03 GMT

PingBack from http://insomniacuresite.info/story.php?id=4388