program selection system

Automated unit testing is the agile software development equivalent of “in-process inspection” in Lean Production systems. xUnit is the generic name given to the family of tools/frameworks used by developers when developing automated unit tests. The community has now had enough experience with using XUnit to start cataloging “best practices” and “not so best practices” as patterns and smells. This tutorial introduces a number of these “test smells”, describes their root causes, and suggests possible solutions expressed in the form of patterns.

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?

The release of NUnit 2.0 was almost 6 years ago. According to Kent Beck, Most folks who port xUnit just transliterate the Smalltalk or Java version. That’s what we did with NUnit at first, too. NUnit 2.0 is as it would have been done had it been done in C# to begin with. Unit testing began to really catch on in .NET. Six years later, many .NET developers are doing unit testing, and many of them cut their teeth on NUnit.