Thursday, July 19, 2007

If yer code ain't tested, the waterfallists win.

Just reporting on untested code is nothin'. How about a tool that *removes* untested code.

Check out the oh-so-provocatively named coverage tool, Guantanamo.

When Guantanamo detects untested code it will actually remove it from a working copy of the codebase. C'mon, if you want to move from the foo-foo world of XP and into the hardcore world Mountain Dew level of extreme it should remove the code from source control. Currently the tool is only available in the Java world, but with most of the XP tools stack (ant, junit, cruisecontrol, jcover) will eventually find it's way into the C# world.

If you're wondering about the quality of your unit tests, and are in the Java world, check out Ashcroft. The same guy who gave us Guantanamo also created this tool for analyzing your unit tests. By checking your tests against a set of guidelines your testing practices become more focused and streamlined.

They are building a 10 Commandments of Unit Tests, here's a direct quote from their site.

  1. I am the class being tested. Thou shalt not test any other class but me.
  2. [Thou shalt write isolated tests]
  3. [Thou shalt not access files during unit tests]
  4. [Thou shalt not write two tests which depend upon each other]

This is good stuff, and I'm looking forward to more of these kinds of tools in the .NET world. Sure we have VS.NET and it's a great tool, but it seems like everything we have is clones of stuff from the Java universe. Are there any tools really unique to .NET that didn't originate as a direct reimplementation of a Java tool?

Submit this story to DotNetKicks