Comments on: Unit Testing in .NET with NUnit http://brennan.offwhite.net/blog/2005/01/24/unit-testing-in-net-with-nunit/ My Experiences with Software Development Tue, 06 Jan 2009 15:10:21 +0000 http://wordpress.org/?v=2.5.1 By: Graeme Foster http://brennan.offwhite.net/blog/2005/01/24/unit-testing-in-net-with-nunit/#comment-112 Graeme Foster Tue, 25 Jan 2005 08:32:44 +0000 http://brennanwp.offwhite.net/blog/?p=73#comment-112 .NET 2.0 introduces partial classes in C#. These let you easily have tests within a class (so you can test private stuff in the class as well as the public interface - I know that's frowned on by some and smiled on by others, but for me it helps get the job done) while still keeping the test code away from the "real" code. Works well for me. For example, we have MyClass.cs containing the class code, and an accompanying MyClass.Tests.cs file which has the unit tests. Everything in that file is enclosed in a #if TEST condition. .NET 2.0 introduces partial classes in C#. These let you easily have tests within a class (so you can test private stuff in the class as well as the public interface - I know that's frowned on by some and smiled on by others, but for me it helps get the job done) while still keeping the test code away from the "real" code. Works well for me.

For example, we have MyClass.cs containing the class code, and an accompanying MyClass.Tests.cs file which has the unit tests. Everything in that file is enclosed in a #if TEST condition.

]]> By: Brennan Stehling http://brennan.offwhite.net/blog/2005/01/24/unit-testing-in-net-with-nunit/#comment-111 Brennan Stehling Mon, 24 Jan 2005 19:44:02 +0000 http://brennanwp.offwhite.net/blog/?p=73#comment-111 I agree. I have read C and C++ code with these directives and it is just insane. But in C the purpose is to allow them to place cross-platform support into the codebase, like including a different header or calling a different threading implementation. It is not as important for languages like C# and Java which has the standardized runtime. Also with Java and C# you can use Ant and Nant scripts which will allow you to automatically strip out some lines of code or ignore some files during the compile process so there is not need for those directives. I agree. I have read C and C++ code with these directives and it is just insane. But in C the purpose is to allow them to place cross-platform support into the codebase, like including a different header or calling a different threading implementation. It is not as important for languages like C# and Java which has the standardized runtime.

Also with Java and C# you can use Ant and Nant scripts which will allow you to automatically strip out some lines of code or ignore some files during the compile process so there is not need for those directives.

]]> By: Chris Peterson http://brennan.offwhite.net/blog/2005/01/24/unit-testing-in-net-with-nunit/#comment-110 Chris Peterson Mon, 24 Jan 2005 19:37:01 +0000 http://brennanwp.offwhite.net/blog/?p=73#comment-110 I find using the separate projects easier than using directives. When maintaining code I hate seeing all different kinds of directives in the main code. I can understand having them if you are working on a bug, but please people get rid of them before the code goes live. I find using the separate projects easier than using directives. When maintaining code I hate seeing all different kinds of directives in the main code. I can understand having them if you are working on a bug, but please people get rid of them before the code goes live.

]]>