Saturday, December 26, 2009

When your unit test is not implemented...


When your unit test is not implemented yet you want to make sure everybody knows about it. One bad way is to throw an exception in the test first line:

public void MyNewTest()
   throw new NotImplementedException();

The reason is that when you see in the report this failure you can never tell if the error comes from the unit test or the application under test...

The good solution is to use a build in feature of your unit test framework. For example, the Ignore attribute in NUnit. If for some reason you have to throw an exception (so the test will be red) at least throw some better error class like "new UnitTestNotImplementedException()".


What's next? get this blog rss updates or register for mail updates!