Notice the attribute FitNesseUrl above. This specifies what page the runner should execute.
The output of the test is a little different than what you get with a unit test: the metrics are page based. I have included a link to the live FitNesse url as well as a static html report of the test run. Of course the Test With menu items work with this so you can Debug and get code coverage.
There is no installer yet. Heck the TestDriven.NET FitNesse Runner has no home. Until it gets a home here is the binary and here is the source. To use it just reference it (and Program Files\TestDriven.NET 2.0\TestDriven.Framework.dll) from your fit fixture project and include this assembly level attribute:
This attribute clues TestDriven.NET into what runner to use. Once we get an installer we can create the registry entries that are normally used to clue TestDriven.NET into what runner to use.
Where do you think the FitNesse plugin’s home should be?6,863 Total Views