Smart Contracts

Updating Solidity code and Testing a Smart Contract

Books on the Blockchain

Publica Self Publishing

Goodbye Contracting

Hello brave new old world...

Ruby-Selenium Webdriver

In under 10 Minutes

%w or %W? Secrets revealed!

Delimited Input discussed in depth.

Monday, 5 July 2010

Specification by Example and Agile Acceptance Testing

I recently attended a great workshop with Gojko Adzic the other week covering 'live documentation', the workshop was called "Specification by Example and Agile Acceptance Testing", check it out on his site (

At the testing consultancy where I work we already routinely use a couple of tools for live documentation as part of the 'Behaviour Driven Testing' (BDT) approach I developed around BDD.

Live documentation tools of this kind include Cucumber, Concordion, FitNesse, SpecFlow, etc. (links below) and provide a way to help ensure the documentation is current and up to date. They get away from the 30 page Word document that's out of date and a nightmare to keep under
version control.

I'm a big fan but wonder how used these tools are over traditional approaches, so my questions:

* Are you using any of these?
* If not why not, if so what drove you to use them?
* If you are using them have you taken the next step and used them to drive automation?