Library tutorials & articles
Test-Driven Development in .NET
By Peter Provost, published on 18 Jan 2006
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 .
Related articles
Related discussion
-
hey developers out there
by pitsophera (0 replies)
-
How can i develop opc server using .net?
by vairajaig (1 replies)
-
Creating a Windows Service in VB.NET
by davidvanr (108 replies)
-
High-Performance .NET Application Development & Architecture
by Manjot Bawa (0 replies)
-
An Introduction to VB.NET and Database Programming
by carlosmen (14 replies)
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
-
Nov
18
15 Minutes of Fame
Dresher, United States
This is a yearly tradition. We select 10 of the favorite speakers from monthly meetings, code camps, and hands on labs. Each one does a 15 minute talk on their favorite .NET technology. This is our 10th anniversary so we plan a gala event with special prizes and refreshments.
Well explained. More about TDD using C# can be found here Link Text
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
This thread is for discussions of Test-Driven Development in .NET.