Library tutorials & articles

Test-Driven Development in .NET

Conclusion

Test-driven development is a powerful technique that you can use today to improve the quality of your code. It forces you to think carefully about the design of your code, and is ensures that all of your code is tested. Without adequate unit tests, refactoring existing code is next to impossible. Very few people who take the plunge into TDD later decide to stop doing it. Try and you will see that it is a Good Thing .

Comments

  1. 12 May 2009 at 20:55

    Well explained. More about TDD using C# can be found here Link Text

  2. 22 Aug 2007 at 12:01

    Hello, would it be possible to post all of the code regarding the "Using Mock Objects - DotNetMock" article.  The page outlines the process and most of the code, but it'd be great to see the UI that is actually being tested against the mocked version - i.e. it is slightly confusing about where the line is drawn on how much of the actual UI is being tested and being able to execute the real code against the mocked code would clarify how the view and the controller interact.

    Many thanks

  3. 01 Jan 1999 at 00:00

    This thread is for discussions of Test-Driven Development in .NET.

Leave a comment

Sign in or Join us (it's free).

Peter Provost

Related podcasts

  • The Past, Present and Future of .NET Unit Testing Frameworks

    Scott gets a rare chance to sit down in person with developers from three .NET Unit Testing Frameworks. Charlie Poole from NUnit, Jeff Brown from MbUnit, Brad Wilson from xUnit.NET as well as Roy Osherove, the author of the upcoming "Art of Unit Testing."

Events coming up

  • Dec 9

    GL.net Group Meeting - December 2009

    Gloucester, United Kingdom

    The beginning of this year holiday season will belong to mocks. Ronnie and Stephen will take us for a tour around exciting world of unit testing.

Want to stay in touch with what's going on? Follow us on twitter!