BDD with JBehave and Selenium

Behaviour Driven Development with Java Nikolay Vasilev 15 July 2011

Content What BDD is? Jbehave JBehave and Selenium Jbehave – Pros and Cons Questions and Answers References

Test-Driven Development (TDD) Approach for developing software by writing tests before writing the code being tested

Test-Driven Development (TDD) Facilitates Software Design Express Software Behaviour Documents the Code

Unit Testing A form of TDD Meets developer’s expectations for the code behaviour Fragile – Too coupled to the implementation Should meet user’s expectations

User’s Expectations Use Cases User Stories preferred in Agile projects Both of them have no validating mechanisms that the code meets user’s expectations

Testing Types and Expectations Application Levels Testing Type Expectations UI / Presentation / … Controls / Services / … Classes / Models / … Code Meets Customer’s Expectations Code Meets Programmer’s Expectations Unit Testing BDD Selenium

DDD and Ubiquitous Language Domain Driven Design Approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts Ubiquitous Language (UL) " A language structured around the domain model and used by all team members to connect all the activities of the team with the software " – Domain Driven Design by Eric Evans.

Executable Documentation The system requirements are usually expressed by textual documentation In the ideal world the documentation uses UL If this documentation was executable, it would be perfect! It would assure that the code continues to meet the expectations in long term

Behaviour Driven Design A TDD approach It is an executable documentation Helps for UL development and usage Clears out the misunderstandings between customers, domain experts, developers, QA team etc. Can be used by everybody involved in a project

BDD as Stories and Behaviour BDD can be used to express Stories and Behaviour Stories Correspond to User Stories Express application behaviour at high level Stories framework needed (eventually) Behaviour (or Spec) Corresponds to expectations at class level Expresses behaviour at service/component level

Stories and Behaviour User Stories Series of acceptance criteria Called scenarios Each scenario has givens , events and outcomes Used in Agile projects Behaviour Expressed as a test method It defines what the application should / shouldn’t do

A Story Structure Narrative As a [some_role_here] I want [some_feature_here] So that [behefit/value_of_the_feature_here] Scenario(s) (this is acceptance criteria) Given [some_initial_condition(s)] When [event(s)_occurs] Then [ensure_some_outcome(s)]

BDD Process Exercise expectations against Matches to Customer QA Domain Expert Developer

BDD Process Create scenarios for expected features Then follow the process: For each scenario describing a feature Run the scenario – it fails (go red ) Define the first step – go red Write down the application code getting the step to pass – go green Refactor the code and repeat steps 4 & 5 for each step until 6 The scenario passes – go green Refactor the application code

BDD Tools C – Cspec C++ – CppSpec, Spec-CPP .Net – NBehave, NSpecify, SpecFlow Groovy – GSpec, easyb, Cuke4Duke PHP – PHPSpec Python – Specipy Ruby – RSpec, Shoulda, Cucumber More…

BDD Tools (Java Related) JBehave – Java annotations based, Test frameworks agnostic Cuke4duke – Cucumber support for JVM JDave – RSpec (Ruby) inspired, Mojo 2 & Hamcrest based beanSpec – Java based easyb – Java based, Specifications written in Groovy instinct – BDD framework for Java, providing annotations for contexts. Inspired by Rspec BDoc - Extracts behaviour from unit tests

JBehave Open Source Java-based BDD Framework Created by Dan North (2003) to compare BDD to TDD Current version 3.4.2 Components JBehave Main JBehave Web

JBehave - Features Pure Java implementation Text-based user stories Annotation-based binding of textual steps to Java methods DI support (Spring, Guice, Pico, Weld) Story reporting (HTML, TXT, XML) User stories localization IDE integration Ant and Maven integration Test frameworks agnostic (JUnit, hamcrest, etc.)

JBehave Web - Features Extension of JBehave providing web integration layer for BDD Features JBehave Queue – allows generic stories to be run asynchronously Web Runner – allows generic stories to be run synchronously Selenium Integration – automation of stories for web apps using Selenium

JBehave – Five Steps Overview Write a story Map steps to Java Configure Stories Run Stories View Reports

JBehave – Five Steps Overview Step 1 – Write a story Narrative : In order to calculate BMI with ease As a doctor I want to have BMI Calculator application Meta : @author Nikolay Vasilev @bg-jug Scenario : Simple BMI calculator validation Given a body mass index calculator When a patient's is with mass 77 kg and height 1.75 m Then patient's body mass index is 25.14285659790039

JBehave – Five Steps Overview Step 2 – Map steps to Java

JBehave – Five Steps Overview Step 3 – Configure stories

JBehave – Five Steps Overview Step 4 – Run stories with:

JBehave – Five Steps Overview Step 5 – View Reports (HTML, TXT, XML)

JBehave – Use Case Body Mass Index Calculator and Classifier Domain Classes

JBehave – Use Case BMICalculator component Computes BMI by the formula: Where BMI – body mass index W – a person’s mass in kilograms h – a person’s height in meters

JBehave – Use Case WeightClassifier component

JBehave Stories Plain-text stories Consists of narrative and multiple scenarios Usually stored as .story file, but this is configurable Narrative Optional As a, In order to, I want to A scenario consists of: Given, When, Then And maps to any of them Possible use of When after Then Scenarios could depend on others scenario GivenScenarios Comments ( !-- )

JBehave Steps Declared as Java annotations Steps annotations @Given, @When, @Then Lifecycle annotations @BeforeStory, @AfterStory @BeforeScenario, @AfterScenario Pending steps @Pending keyword

JBehave Steps Step annotations take regex See Code Example Alias(es) – mapping various text strings to one method @Alias, @Aliases See Code Example Parameter Injection Captured values are converted to method parameters @Named – Explicit mapping of values to parameters See Code Example

JBehave Configuration Everything is configurable (powerful) Everything has defaults (makes life easy) Main Configuration How to load stories (classpath, file, etc.) Story file naming and parsing configuration Error strategy and Pending error strategy How to handle failure and missing steps Step Configuration Parameter Converters

JBehave Configuration Embedder and Embeddable

JBehave Configuration Jbehave provides two Embeddable implementations ConfigurableEmbedder InjectableEmbedder ( example AnnotatedEmbedder ) JUnit-enabled Embeddables Ran like JUnit tests JUnitStory - one-to-one mapping with the textual story JUnitStories - many-to-one mapping Exntending Embedder EclipseEmbedder example

JBehave – Advanced Parameterized Scenarios Examples: - required in the story Followed by table of parameters The mapped parameters should be surrounded by ' < ‘ and ' > ‘ in the story Table examples require named parameters for the step candidates to be matched to the Java methods The step annotation pattern must hold the verbatim textual step The tables could be loaded from external resources

JBehave – Advanced Non-English Keywords Tabular parameters Multiline values Example : Given tab e|--------------------------------- B|--------------------------------- G|--------------------------------- D|----------0--0------------------- A|-0--2--3----------2--0-----0--0– E|------------------------3-------- When the guitar plays Then the following notes will be played A0 A2 A3 D0 D0 A2 A0 E3 A0 A0

JBehave – Advanced Meta information Meta Followed by name value properties separated by @ Example: Meta filtering Used for selecting of stories Meta @author Nikolay Vasilev @organization Bulgarian Java Users Group -author *Vasilev

JBehave – Advanced Ant tasks and Maven plugin Integration with Spring, Pico, Guice Reporting options Console, Text, HTML, XML Default reports location in a Maven project: ${project.dir}/target/jbehave Example Test integration (JUnit and TestNG) See AnnotatedEmbedder example

JBehave Reporting Options Reports HTML Report

JBehave Reporting Options Failing Story HTML Report

JBehave Reporting Options Pending Steps Story HTML Report

JBehave Reporting Options Parametrized Story HTML Report

JBehave – Eclipse Plugin Home Page Status: In development Non-trivial installation (next slides) Not very rich functionality but makes the life easier Provides Basic highlighting On match, the step in the story is linked to the mapped method Certain autocomplete when writing stories

JBehave – Eclipse Plugin Example Keywords highlighting “ Jumping” from story to Steps class Autocomplete

JBehave – Install Eclipse Plugin Download the plugin

JBehave – Install Eclipse Plugin Eclipse > File > Import

JBehave – Install Eclipse Plugin Existing Projects into Workspace

JBehave – Install Eclipse Plugin Select archive file: > Browse

JBehave – Install Eclipse Plugin Select archive file > Open

JBehave – Install Eclipse Plugin Select archive file:

JBehave – Install Eclipse Plugin Finish

JBehave – Install Eclipse Plugin Project Editor > Select the new project

JBehave – Install Eclipse Plugin File > Export

JBehave – Install Eclipse Plugin Select > Deployable plug-ins and frag…

JBehave – Install Eclipse Plugin Select the Plug-in & Chose Install into host

JBehave – Install Eclipse Plugin Restart Eclipse (Chose ‘Yes’)

JBehave – Install Eclipse Plugin The story files are with different icon 

JBehave – Install Eclipse Plugin Not “recognized” stories > Select + Right Click > Open With > Behavior Editor

JBehave – Install Eclipse Plugin Now the keywords are highlighted

JBehave and Selenium Selenium A suite of tools to automate web app testing across many platforms. Abstracts away the interaction with the web layer (browser/server) Java, Perl, C#, C, etc. Selenium Object Tested WebApp Selenium RC Server Browsers

JBehave and Selenium Selenium would let us focus on testing the web-app functionality Although, steps classes get cluttered by selenium calls Steps Selenium Object Tested WebApp Selenium RC Server Browsers Stories

JBehave and Selenium JBehave and Selenium First thought - Steps will interact with the selenium object from the steps classes Steps Selenium Object Tested WebApp Selenium RC Server Browsers Stories

JBehave and Selenium Page Objects Pattern Page object represent the services offered by a page Hides the knowledge of the page structure from the developer Steps Selenium Object Tested WebApp Selenium RC Server Browsers Stories Page Object

JBehave and Selenium Rules of Thumb Keep assertions in the steps mapping classes Keep selenium interaction in the page objects Stories should address the functionality which the pages offer

JBehave and Selenium What do we need to integrate JBehave and Selenium SeleniumConfiguration (part of JBehave Web) @BeforeScenario, @AfterScenario steps Responsible of start/stop selenium object Pages and Steps implementation Running selenium tests in an automated way (maven – integration-test phase) Tip: Configure Firefox for testing with Selenium

Use Case – Web Testing Web app for our Use Case 2 JSPs – one for main form, another for result In order to run it are required: Run the web app on a web server Run the Selenium RC server with the selenium profile (see tip from prev. slide) Execute WebBmiCalculatorStories embedder as JUnit test

Use Case – Web Testing Main form

Use Case – Web Testing Result page

Use Case – Web Testing The main form is also error page

Use Case & Examples Code Use Case Code – Consists of 3 Maven 2 projects jug-bg-bdd-domain Domain Classes of the Application jug-bg-bdd-jbehave JBehave Examples (depending on the first project) jug-bg-bdd-web JBehave & Selenium Examples (depending on the first project)

Use Case & Examples Code Source Code could be found on: http://code.google.com/p/bg-jug-resource-repository/

References BDD Wiki Jbehave JBehave Tutorial Dan North – Introducing BDD Dan North - What’s in a Story? [pdf] BDD in Java and Groovy [pdf] TDD Beyond Junit BDD in a Nutshell

References Ryan Greenhall – BDD by Example Localizing JBehave Scenarios Eric Evans - "Domain-Driven Design: Tackling Complexity in the Heart of Software", Addison-Wesley JBehave Site :: Dependency Injection JBehave + Spring + Selenium Example

References Selenium Project Page Objects Pattern Creating Firefox Profile for Selenium RC Tests JBehave Site :: Using Selenium BDD with JBehave Web 3, Selenium and Maven 2 for OS X Leopard Nice JBehave + Selenium + Maven Example Selenium Tutorial to set up a Selenium Grid

BDD with JBehave and Selenium

More Related Content

What's hot (20)

Similar to BDD with JBehave and Selenium (20)

Recently uploaded (20)

BDD with JBehave and Selenium

Editor's Notes