FitNesse out of the box does not seem to work for teams! In this demo I’ll show how to set up FitNesse so that development teams can do the following:
- Organize their Stories, Acceptance Criteria and Acceptance Test better
- Create different levels of test suites to give feedback at different levels
- Version control the FitNesse wiki with their source code
- Inline editing of their FitNesse pages, with out having to worry about Wiki syntax
- Integrate FitNesse with their builds, so that they can run their acceptance tests as part of their Continuous Integration loops
- Integrate FitNesse with CruiseControl or other CI servers to that the team can see the acceptance test results from the build
- Execute their acceptance tests against the server side components in a web/app server
- Demo DBFit, a standard library of fixtures for basic DB operations. Mostly used for set-up and tear-down sets of acceptance tests
Process/Mechanics
Interactive demo about these features of FitNesse from my laptop.