Managing requirements with FitNesse
Versioning of requirements
In FitNess requirements are versioned … in the following example Version 001 is stable and Version002 can be further specified.
For preparing a new version, we make a copy of the file system:
5.2 Requirements are directly referenceable
Via URL, all requirements are versioned referenceably.
A UseCase
This is an example for a UseCase, the acceptance tests are described below.
The associated acceptance test
Search for requirements
FitNesse features the possibility for a full text search:
A view
Here you can see a view with chapters in hinged position:
And here the chapter “Community Suche” (community search) is opened … all assigned requirements are listed one below the other.
The Edit-Mode shows that the requirements are only referenced.
Test support
In the meaning of FitNesse, all requirements are TestSuites. So in the FitNesse manner, requirements can be tested together on any level. A generic fixture presents the test instruction to the tester.
You get a fine test summary for the individual test...
and for all realized tests and retests ...
What's still missing
The tooling suggested above already works for small projects. But it has the following two gaps: Semi-automatic test support only prototypical: At the moment, the test support works only prototypical. The test instructions are just realized by swing - a web based realization is possible but complex and not yet implemented.