Storytest-Driven Development

Storytest-Driven Development involves determining if features of a system work according to a customer's expectations. There are many ways to implement Storytest-Driven Development, including using XML, Excel or simple languages. A typical challenge is to empower customers with tools that let them define Storytests (a.k.a. Acceptance Tests) without working with programmers. Another challenge is to practice Storytest-Driven Development, in which Storytests are specified before code is written.

Flavor: dialogue
45 to 60 minutes
The workshop coaches will lead a discussion about Storytest-Driven Development, sharing their stories and perspectives, and describing what has and hasn't worked well. In addition, we'll discuss commercial GUI testing tools and their alternatives. We'll conclude the discussion by observing how Storytest-Driven Development can positively impact a system's design.

ID: 17A

Flavor: demonstration
15 to 120 minutes
We'll demonstrate FIT (http://fit.c2.com), Ward Cunningham's excellent open-source testing tool that lets non-technical users (i.e., typical customers) specify tests easily using descriptive text and a variety of simple tables. We will see how the resulting work produces what we call "executable documentation."

ID: 17B

Flavor: challenge
1 to 6 hours
Participants will be given the challenge of writing FIT tests for a sample program, using the Storytest Driven Development practice.

ID: 17C

Flavor: deployment
1 to 2 hours
Our coach will guide your team in setting up FIT/Fitnesse (http://www.fitnesse.org), including Industrial Logic's enhancements to Fitnesse.

ID: 17D

Next 5 Activities

·	Unit Testing Legacy Code
·	Mock Objects
·	Unit Testing Tool
·	Test-Driven HTML
·	The Refactoring Challenge

Catalogs

·	Activity Catalog
·	Experience Catalog
·	Workshop Catalog

Facebook Twitter Twitter linked in LinkedIn