Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Writing Executable Specifications

Writing Executable Specifications



Thomas Sundberg emphasizes the need for writing executable specifications demoing on example using Cucumber.


Thomas Sundberg is a consultant based in Stockholm, Sweden. He has taught programming at The Royal Institute of Technology, KTH, one the leading technical universities in Sweden. Thomas is also a speaker at eXtreme Programming XP, Agila Sverige, Öredev, Turku Agile Day, Agile Central Europe, GeeCON, Java Developer Day, Agile By Example, Scandinavian Developer Conference and Agile Testing Days.

About the conference

Agile Cambridge is THE learning and collaborating conference for Agile and Lean practitioners in the East of England. The event also draws participants from across the country, mainland Europe and further afield. It is one of the most successful Agile conferences in the UK.

Recorded at:

Feb 19, 2013

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Tip on tooling for biz folks

    by Johnny FromCanada,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    During the coding demo (~30:45) a series of questions come up about where the scenario files should live and who would write them. The presenter contends that _ideally_ biz folks would. But likely devs would write them and bring in biz folks for validation, since the specs are persisted with the source code, (hence not readily accessible to biz folks).

    However, there are tools to help with this problem, allowing biz folks to specify the scenarios and establish traceability to the code level. (Such tools perhaps did not exist at the time of the presentation).

    E.g., Hindsight Behave has a plugin for Jira, where the PO/BA can specify the scenarios (acceptance tests), aggregated into features. These scenarios can be linked (many-to-many) to Jira issues (stories). And per existing Jira-VCS integration, Jira issues can be linked to their implementing code.

    Hope that helps someone.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p