Download Test Driven .NET Development with FitNesse

Using business domain objects directly
and start programming test-specific functionality in test pages for the
sake of reducing fixture code. I think that this is wrong and that FitNesse
pages should work more as specifications than scripts. You shouldn't
sacrifice clarity in order to not have five more lines of code. Test specific
functionality and coordination should stay in fixtures, that is where it
belongs. Describing how a test is executed rather than what is being tested
is one of the most common reasons why teams fail to get the full benefits
of FitNesse. I wrote a lot more on this subject in Bridging the Communication Gap [1].
176