November 30, 2004

JBehave V

The idea with JBehave is to start with the story on story cards. When it comes to implement a story, the customer (business coach) should write the acceptance criteria for the story and then parse them into JBehave. This creates given, event and outcome classes. The developer then codes the behaviour expected in these classes. The context is specified using Mock objects in the givens. The call to the class being tested is written in the event class. The checking of outcomes is written in the outcomes class. For each class, a behaviour (JUnit) class is written.

Mocks.jpg

As the classes are implemented, the mocks in the context are replaced with real classes until all the mocks have been removed.

Posted by chrismatts at November 30, 2004 5:24 PM