TDD Clinic: NUnit
It has been over six years since the first release of NUnit 2.0. In that time there have been literally millions of tests that have been authored. Many of these tests have become invaluable resources for their teams. Unfortunately there have been others that have not been maintained and were viewed as a waste of effort. What separates tests that are maintained from tests that are discarded? This session describes 7 key lessons that have been proven to increase the readability of the tests as well as their maintainability. Taking these lessons into account can make the difference between tests which become a team burden and tests which become an invaluable team resource.
Lesson highlights include:
• A discussion on the impact of test and test fixture size
• The use of attributes like [ExpectedException], [Setup], and [TearDown]
• The impact of dependency injection on unit testing
This session will be lecture style but will use many code examples to demonstrate the important aspects of the lesson.
Update: I have attached an outline of the 7 lessons as a file attachment.
** Update #2: ** I was just looking through the PDF and realized the pages with code on them did not render correctly. I will update it again on Monday.