Welcome to part two of our series on building a Windows application using test-driven development (TDD). In the previous article we drove the design of our entity classes and data access layer by means of unit tests. The unit tests acted more as specifications for the system rather than tests, since...

JP Hamilton has posted a brief blog post on how he unit tests WinForms . Looks nifty, especially if you use a pattern like Model-View-Presenter for your forms. His rationale is that if you keep on testing only the presenter and mocking out the view in your unit tests, your forms code still gets zero...

The previous incarnation of that Microsoft article was heavily panned by critics and in a rare move, Microsoft actually pulled it out of its developer web site. I didn't realise it but Microsoft actually replaced it with one written by Jeffrey Palermo -- http://msdn2.microsoft.com/en-us/library/aa730844...

This InfoQ link on pipelined CI got my attention because it was something that I can relate to. The project we're working on used to build on our CruiseControl.NET build server in only three minutes; now it's taking more than 18 minutes to complete. And it's a dual-core 2 GB machine at that...

Have you heard of the term cyclomatic complexity ? I had my first encounter with it in the current project we're doing at work. One of the senior guys in our project set up our build server, with CruiseControl.NET invoking a tool called SourceMonitor and analyzing source code complexity. Basically...