Behaviour Driven Development

Behaviour Driven Development Carsten Nielsen 2011-11-23

Test Driven Development
Automation makes life easier
Refactoring/extending becomes safer
Faster development and better software
Why? How can we test something theat don't exists? But hey! Test? It's about Design!

It's Evolution Baby!
With ”Tests” we're designing the software/product.
We're describing it's behaviour.
Test Driven Development Behaviour Driven Development

And there were Tests...
The customer wants us to build that awesome new video-portal with function X and technology Y and In The Cloud!
We're talking with the customer about the How/When/Budget.
The customer defines 2 gazillion pages of specs.
We're sitting on the specs and start coding our tests.
Project proceed...Tests passes...We're happy!.
Is the customer happy? Oops! Design-Fail! What about the Why?

Obscured by code Is this readable, understandable and acceptable? class FixturesTest extends sfPHPUnitBaseTestCase { public function _start() { new sfDatabaseManager(ProjectConfiguration::getApplicationConfiguration('frontend', 'test', true)); Doctrine_Core::loadData(sfConfig::get('sf_data_dir').'/fixtures'); } public function test1() { $name = 'foo'; $model = Doctrine::getTable('SomeModel')->findByName($name); $this->assertTrue( is_object ($model)); $this->assertEquals('SomeModel', get_class ($model)); $this->assertEquals($name, $model['name']); } } Can the customer understand this?

Babelfish!
Use same vocabulary for
Developers
Testers
Analysts
and our Customers!
Instead of code: And: Force them all think about the Why and Value!

Once upon a time... A userstory: Editor can login As a editor I want to be able to login into the backend So that I can edit my personal events Thats a role, an action and a value. In order to edit my personal events As a editor I need to be able to login into the backend Yes! Value! Alternative pattern with focus on value:

Desire! Tension! Action! A scenario: Login as reistered user Given I am on «/login» When I fill in «username» with «slartibartfass» And I fill in «password» with «42» Then I should see «Welcome!» And I should not see «Login» And this is testable – readable - usable! Other language needed? Givet jag är på «/login» När jag fylla in «username» med «slartibartfass» Och jag fylla in «password» med «42» Då skulle jag se «Welcome!»

Welcome to Planet Gherkin!
Domain Specific Language
Create the vocabulary with your client
Let the client write the stories/scenarios
Let the client accept the scenarios
Perfect for agile workflows
Drop the spec-definition-bible and save some trees!

A demonstration.
Behat – a BDD-framework for php
Mink – an abstraction layer for browser-engines
Test in any language you want!
Attention!
A terminal session is going to start – non-coders are allowed to take a mental break ;-)

Go digging!
For PHP: Behat
For Java: Jbehave
For Ruby: Cucumber
For Python: Lettuce
For Perl: Test::Cukes
Ahh - ok and for dotnet: SpecFlow

Thanks!
Ressources:
Dan North – www.dannorth.net
Konstantin Kudryashov – www.everzet.com
www.behat.org Carsten Nielsen carsten@redpill-linpro.com @phreaknerd

Behaviour Driven Development

by Carsten Nielsen on Jan 24, 2012

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 4

Statistics

Behaviour Driven Development — Presentation Transcript

http://a0.twimg.com	2
http://www.hanrss.com	2