I have watched the evolution of Joe Ocampo‘s requirements testing framework with eager anticipation. As most who have tried to use it know, Fitnesse just doesn’t quite hit the mark for expressing requirements into tests and Joe’s work is a promising bridge for that gap.
This post gives the best intro into the basic idea behind Joe’s framework.
Now that Joe is moving his project into CodePlex as open source, we have the promise of even wider adoption. A natural evolution of this idea may go like this.
- Developers love it and begin expressing their stories this way in their unit tests.
- Someone creates an Excel->XML->Code generator and gets their product owner to generate classes from specification criteria.
- Someone builds a requirements editor that is almost good, but cludgey.
- Steel Trace sees the potential and builds requirements to Behave# adapters into their product.
- A new Scrum for Team System template is released with Orcas with support for story definition the way it should have been the first time.
- The stories entered in TFS by product owners can now dynamically generate Behave# assemblies (of course, this wont be supported by MS, but we’ll figure it out).
The end game here is that requirements are compiled into code resulting in instant automated acceptance and regression testing. I can practically hear angels singing.