FITnesse and .NET

FIT is definitely something I have to dig into in the near future. I’m trying really hard to make the shift to, and understand Test-Driven Development. FIT is something that will definitely come in handy in persuading customers to see the benefits of TDD. FIT is used for collaboration and communication. The current implementations are based on a specific wiki, where customers, testers and programmers learn what their software should do, and to automatically compare that to what it actually does do. It compares customers’ expectations to actual results. It’s an invaluable way to collaborate on complicated problems (and get them right) early in development, according to James Shore.

In simple words, imagine yourself a html page with explanation of what some part of the application should do. Then imagine a table with a short sentence, an expected result and the actual result. Just like in your (nUnit) unit tests. This works really great for customers, as they can see for themselves what’s happening in their application. And it’s also great as being a part of the customer’s acceptance tests.

FitNess is the .NET implementation and Cory Foy has written a basic tutorial to give you an idea of what should be done. I don’t think it was explained this clearly before, including screenshots. So it’s definitely a good start to get an idea, if you can’t get through the multiple pages of info on the FitNess site.