Comments on: TDD with Visual Studio – to do or not to do http://blog.nwcadence.com/2007/11/tdd-with-visual-studio-to-do-or-not-to-do/ Thoughts on VSTS, Sharepoint and other collaborative technologies Sun, 04 Apr 2010 05:36:54 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: MikeAzocar http://blog.nwcadence.com/2007/11/tdd-with-visual-studio-to-do-or-not-to-do/comment-page-1/#comment-16 MikeAzocar Wed, 14 Nov 2007 20:57:48 +0000 http://blog.nwcadence.com/2007/11/08/tdd-with-visual-studio-to-do-or-not-to-do/#comment-16 I agree with some of the points each of you made. Chris. You are right, Resharper makes TDD so much easier. Jeff. I agree that there is more than one way to be successful with TDD. You have to be flexible and take the practices that work best for the project and the development team. I agree with some of the points each of you made.

Chris. You are right, Resharper makes TDD so much easier.

Jeff. I agree that there is more than one way to be successful with TDD. You have to be flexible and take the practices that work best for the project and the development team.

]]> By: Jeff Levinson http://blog.nwcadence.com/2007/11/tdd-with-visual-studio-to-do-or-not-to-do/comment-page-1/#comment-10 Jeff Levinson Wed, 14 Nov 2007 15:22:49 +0000 http://blog.nwcadence.com/2007/11/08/tdd-with-visual-studio-to-do-or-not-to-do/#comment-10 Thanks Chris, sorry it took so long to write back. Your points are excellent but... One of the things about this view is that there is only one way to do it "correctly". I like to think that even without following TDD to the nth degree that developers can get benefit out of it. And there are plenty of add-ins that work with unit testing in Visual Studio. Granted, we would all like to see more built in but I don't think Microsoft can ever really compete with the full resources of the open source community so their add-ins are a blessing! :) Thanks Chris, sorry it took so long to write back. Your points are excellent but… One of the things about this view is that there is only one way to do it “correctly”. I like to think that even without following TDD to the nth degree that developers can get benefit out of it. And there are plenty of add-ins that work with unit testing in Visual Studio. Granted, we would all like to see more built in but I don’t think Microsoft can ever really compete with the full resources of the open source community so their add-ins are a blessing! :)

]]> By: Team System News : VSTS Links - 11/14/2007 http://blog.nwcadence.com/2007/11/tdd-with-visual-studio-to-do-or-not-to-do/comment-page-1/#comment-8 Team System News : VSTS Links - 11/14/2007 Wed, 14 Nov 2007 13:31:43 +0000 http://blog.nwcadence.com/2007/11/08/tdd-with-visual-studio-to-do-or-not-to-do/#comment-8 [...] Jeff Levinson on TDD with Visual Studio - to do or not to do. [...] [...] Jeff Levinson on TDD with Visual Studio – to do or not to do. [...]

]]> By: Chris Brandsma http://blog.nwcadence.com/2007/11/tdd-with-visual-studio-to-do-or-not-to-do/comment-page-1/#comment-6 Chris Brandsma Thu, 08 Nov 2007 19:56:13 +0000 http://blog.nwcadence.com/2007/11/08/tdd-with-visual-studio-to-do-or-not-to-do/#comment-6 Nice article, but two things: 1. NUnit and MBUnit are generally preferred over MSUnit by 95% of the community. MSUnit has a few nasty bugs in that still haven't been addressed as of VS 2008. See Roy Osheroves blog. http://weblogs.asp.net/rosherove/archive/2007/10/16/unit-testing-in-vs-2008-still-not-there.aspx Pick up Test Driven.Net or ReSharper for test integration. Check that, whatever you do, pick up ReSharper. You wont be sorry. 2. Proper unit testing cannot be done without mock object support (which is not included in MSUnit, NUnit, or MBUnit). Check out Rhino Mocks for that. http://www.ayende.com/projects/rhino-mocks.aspx 3. Understanding Unit Testing is the easy part. Figuring out how to write testable code is the hard part. If you are looking for a place to start, learn about "Separation of Concerns". Jeremy Miller has a nice post on it here: http://codebetter.com/blogs/jeremy.miller/articles/129542.aspx After that, study MVP and MVC as a starting point for doing just that. Nice article, but two things:

1. NUnit and MBUnit are generally preferred over MSUnit by 95% of the community. MSUnit has a few nasty bugs in that still haven’t been addressed as of VS 2008. See Roy Osheroves blog. http://weblogs.asp.net/rosherove/archive/2007/10/16/unit-testing-in-vs-2008-still-not-there.aspx
Pick up Test Driven.Net or ReSharper for test integration.

Check that, whatever you do, pick up ReSharper. You wont be sorry.

2. Proper unit testing cannot be done without mock object support (which is not included in MSUnit, NUnit, or MBUnit). Check out Rhino Mocks for that.
http://www.ayende.com/projects/rhino-mocks.aspx

3. Understanding Unit Testing is the easy part. Figuring out how to write testable code is the hard part. If you are looking for a place to start, learn about “Separation of Concerns”. Jeremy Miller has a nice post on it here:
http://codebetter.com/blogs/jeremy.miller/articles/129542.aspx

After that, study MVP and MVC as a starting point for doing just that.

]]>