Lately I've been trying to focus on how to make testing work better at our company. We've fully integrated our testers into the Scrum teams, but there's still some things I feel is missing. Especially related to the tools/frameworks we use for testing. One of the things I'm looking into is Fit and FitNesse (Framework for Integrated Test) created by Ward Cunningham in 2002. The first time I got an introduction to Fit was in Nils Christian Haugen's presentation at JavaBin back in March. This got me very excited, but I've hadn't had time to look enough into it, but now I think I will.

In essence Fit is a framework that lets your user stories's story tests (or acceptance tests) to be automatically tested/verified. The way you do this is by using a table structure (as showed on the left) to give in values and expected outcome. This is a very nice way of working with tests from a customer perspective. Everyone can understand this by having a short introduction to how it works.

Much like you do with unit tests, this process is automated. The preferred way of authoring unit tests is by using Test Driven Development (TDD). Similarly, working with Fit you can use Story Test-Driven Development (STDD). I really find this way of working to be very interesting and I hope to try this out live soon. Hopefully I can post some more articles on this later when I have some actual experience with it

David Hussman does a great job describing Fit in his presentation.