Comments on: Incorporating NUnit into the Culture http://MarkFreedman.com/index.php/2008/07/16/incorporating-nunit-into-the-culture/ Productivity through technology, and other related topics. Wed, 08 Sep 2010 13:03:52 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Harry Taningco Jr. http://MarkFreedman.com/index.php/2008/07/16/incorporating-nunit-into-the-culture/comment-page-1/#comment-432 Harry Taningco Jr. Thu, 24 Jul 2008 19:06:46 +0000 http://MarkFreedman.com/?p=100#comment-432 To answer your questions directly: (1) If you have time, those who are exposed to the existing systems can do so. It can tend to be time consuming depending on the size and complexity of your overall system. Mocking objects are usually hand in hand with unit testing. It's fairly simple as long as you already have interfaces in place and your system is prepped for loose coupling. (2) That's a judgement call, although I agree with the article that you can assume existing production systems are clean, but to a certain extent - it can also be very helpful in finding bugs not yet found. I would think that it would only help instead of hurt. (3) Mocking is essential, but can be avoided - it all depends on how you want to integrate it overall and how your current system is architected. Is it loosely coupled or is it tightly integrated to external resources (db, networking, etc) (4) Depends on your team, you would know better each team member's style and if it would benefit them to do it one way or another. *Note: You can use NUnit integrated into Visual Studio during your build process etc. - this the fully integrated way of doing it. or you can do it, the way I like to do it - where you have the TestFixture in your solution, etc. but not have it involved in the build process, just use NUnit to test your Unit Test Cases individually. In this latter scenario, you won't be fully TDD, but well on your way to transitioning your team towards it. To answer your questions directly:
(1) If you have time, those who are exposed to the existing systems can do so. It can tend to be time consuming depending on the size and complexity of your overall system. Mocking objects are usually hand in hand with unit testing. It’s fairly simple as long as you already have interfaces in place and your system is prepped for loose coupling.
(2) That’s a judgement call, although I agree with the article that you can assume existing production systems are clean, but to a certain extent - it can also be very helpful in finding bugs not yet found. I would think that it would only help instead of hurt.
(3) Mocking is essential, but can be avoided - it all depends on how you want to integrate it overall and how your current system is architected. Is it loosely coupled or is it tightly integrated to external resources (db, networking, etc)
(4) Depends on your team, you would know better each team member’s style and if it would benefit them to do it one way or another.

*Note: You can use NUnit integrated into Visual Studio during your build process etc. - this the fully integrated way of doing it.
or you can do it, the way I like to do it - where you have the TestFixture in your solution, etc. but not have it involved in the build process, just use NUnit to test your Unit Test Cases individually. In this latter scenario, you won’t be fully TDD, but well on your way to transitioning your team towards it.

]]>