30
Behaviour Driven Development with Cucumber for Java

Behaviour driven development

Embed Size (px)

Citation preview

Page 1: Behaviour driven development

Behaviour Driven Development with Cucumber for Java

Page 2: Behaviour driven development

BDDDomain Driven Design - DDD● Common understanding● Common language● Test Driven Development - TDD● Good technical practices● Small steps● Combined → Behaviour Driven Development

Page 3: Behaviour driven development

Test automation

Test Driven Development, TDD – Develop it the right way Behaviour Driven Development, BDD – Develop the right thing

Page 4: Behaviour driven development

Three core principles• Business and Technology should refer to the same system in

the same way• Any system should have an identified, verifiable value• Up-front analysis, design and planning all have a diminishing

return

Page 5: Behaviour driven development

Common languageUsed by all involved• Customer• Developers• Others?

Page 6: Behaviour driven development

Verifiable value• Protect revenue• Increase revenue• Manage cost• Increase brand value• Make the product remarkable• Provide more value to your customer

Page 7: Behaviour driven development

Big design up-front• No big design up-front• The further you plan ahead, the less accurate you will be

Page 8: Behaviour driven development

Three questions• What is the most important thing the system should do?• What is the next most important thing the system doesn't do

yet?• If we were to switch off the system, where and what would be

the biggest impact?

Page 9: Behaviour driven development

Time to create a specification

Page 10: Behaviour driven development

Time to create a specificationWhen are we done?

Page 11: Behaviour driven development

Interpret and translate We need to read the spec. Understand it Translate it into code Parse and execute it? No, not all specs are created equal

Page 12: Behaviour driven development

Solution Write specifications so Translations isn't needed It is possible to execute them

Page 13: Behaviour driven development

Format• Given – Setup the system• When – Change the state of the system• Then – Verify the new state

Page 14: Behaviour driven development

Tools

Page 15: Behaviour driven development

Audience Readers Customers Developers Maintainers Product owner Developers

Page 16: Behaviour driven development

Why Cucumber

It is one of the least technical tools It is a very active open source project It supports a variety of languages

Page 17: Behaviour driven development

A concrete exampleFeature: Life of IT guysIn order to get good salaryAs a it guyI want to keep my boss happy

Scenario: I am a testerGiven I am a bad testerWhen I go to workThen I mess with itAnd my boss fires meBut the developer likes me

Page 18: Behaviour driven development

Advantages

The format is● Easy to read● Easy to understand● Easy to discuss● Easy to parse

Page 19: Behaviour driven development

Parse and execute

● A parser is developed● Add native code to implement the steps Setup – Given Execute – When Assert - Then

Page 20: Behaviour driven development

Write a step definition in Java@Given("^I am a bad tester$")public void I_am_a_bad_tester(){System.out.println("@Given--I am a bad tester");}@When("^I go to work$")public void I_go_to_work(){System.out.println("@When---I go o work");}@Then("^I mess it$")public void I_mess_with_it(){System.out.println("@Then--I mess it");}@And("^my boss fires me$")public void my_boss_fires_me(){System.out.println("@And---my boss fires me");}@But("^the developer likes me$")public void the_developer_likes_me(){System.out.println("@But--the developer likes me");Assert.assertTrue(false);

}

Page 21: Behaviour driven development

Run it and watch it fail

Page 22: Behaviour driven development

Write code to make the step pass@Given("^I am a [a-zA-Z]{1,} tester$")public void I_am_a_bad_tester(){System.out.println("@Given--I am a bad tester");}@When("^I go to work$")public void I_go_to_work(){System.out.println("@When---I go o work");}@Then("^I [a-zA-Z]{1,} it$")public void I_mess_with_it(){System.out.println("@Then--I mess it");}@And("^my boss [a-zA-Z]{1,} me$")public void my_boss_fires_me(){System.out.println("@And---my boss fires me");}@But("^the developer [a-zA-Z]{1,} me$")public void the_developer_likes_me(){System.out.println("@But--the developer likes me");

}

Page 23: Behaviour driven development

Run it again and see the step pass

Page 24: Behaviour driven development

Why is Cucumber better● Compared to well known tools like JUnit?● It isn't, it's just easier to read for non coders● The readability has increased● Communication is easier

Page 25: Behaviour driven development

Benefits

● Less unnecessary work● Better regression tests● Less speculative work● Less re-work

Page 26: Behaviour driven development

Maintenance Maintained together

● Specs● Tests● Code

Maven Continuous Integration, CI

Page 27: Behaviour driven development

Tips Always use the a common language Don't over specify – start easy Never specify implementation details

Page 28: Behaviour driven development

Do not focus on tools

• They will never solve the problem• A fool with a tool is still a fool

Page 29: Behaviour driven development

Resources Cucumber - http://cukes.info/ Selenium - http://seleniumhq.org/ Maven - http://maven.apache.org/ Jenkins - http://jenkins-ci.org/ Blog

-http://thomassundberg.wordpress.com/

Page 30: Behaviour driven development

Thank You