Martin Krieger

Until very recently I did not know about the acceptance test framework Fit (Framework for Integrated Test) and its Wiki-GUI FitNesse. But now they’ve been brought to my attention both by Stefan Lieser, who made a very good presentation at Bonn-To-Code, and by a company with long experience using this system for their Java projects.

FitNesse supports two different test systems. Besides the traditional Fit there is the new Slim system. Both have advantages and disadvantages - as explaned e.g. in this video by Gojko Adzic.

It’s very easy to switch between the systems in Java. Adding !define TEST_SYSTEM {slim} selects Slim and !define TEST_SYSTEM {fit} selects Fit. Since Fit is the default, this setting could be omitted.

Using .NET it gets a bit more complicated: Fit for .NET is included in FitNesse. To use it you have to set some settings. On the other hand, to use Slim a separate Download is needed. And there are other, these, settings necessary. Also the default path (classes, fitnesse.jar) has to be removed from the root page (resulting in non-functioning Java tests…).

What a mess. I therefore developed a small utility, which acts as a proxy between FitNesse and the separate test systems. If DotNetProxy.exe and DotNetProxy.exe.config are copied, for example, into the FitNesse\dotnet folder, with the settings in DotNetProxy.exe.config adjusted to the actual system, then

!define TEST_SYSTEM {slim}
!define COMMAND_PATTERN {dotnet\DotNetProxy.exe %m %p}

is enough for Slim .NET. For Fit one only has to remove or change the TEST_SYSTEM definition from these settings.

DotNetProxy.zip