1. Introduction to the topic, and presenters
2. Presenters summarise a User Story to the group
3. Presenters play the role of customer with participants playing the part of the team - guided to ask appropriate questions to capture examples that illustrate the story
4. Presenters exchange roles with the participants and elaborate the first example for the user story into an acceptance test (captured in plain text)
5. The group splits into pairs to practice writing the second acceptance test
6. Several pairs’ acceptance tests are collected in order to discuss with the group
7. Presenters show their version of the second acceptance test
8. Presenters show how these are sometimes expressed using a table-heavy approach in FitNesse
9. Presenters then show how to represent these tests so that they look almost identical to the plain-text tests in FitNesse (using a soon to be released Fixture)…
10. Presenters then show how these tests can also be written in code with a fluent API
11. Group discussion of alternatives and reflection on learning points

Notes: a) The yet to be publicly released Fit fixture has been in use on a large enterprise programme of development with one of our clients

b) For the benefit of the reviewers, you can see illustrations of using code to express acceptance tests here: http://bitbucket.org/testingreflections/jnarrate/src/tip/JNarrateExample... http://bitbucket.org/testingreflections/jnarrate/src/tip/JNarrateExample...