Frédérick Ros

Senior Manager, aMaDEUS

Dev addict

 @sl33p3r

 +Frederick Ros

56%

Communication Breakdown

Maximize
the
communication

How ?

Software behaviour

must be described

in a user readable manner

Describe feature
in
natural language

But …

• Use a structure
• Use code as glue

Features

• Expressed in a file
• Described using free form text
• Defined through scenarii

Feature example

Feature: Division
  In order to avoid silly mistakes
  Cashiers must be able to calculate a fraction

  Scenario: Regular numbers
    Given I have entered 3 into the calculator
    And I have entered 2 into the calculator
    When I press divide
    Then the result should be 1.5 on the screen
  

Given / When / Then en

Soit / Lorsque / Alors fr

Angenommen / Wenn / Dann de

前提 / もし / ならば ja

...

I CAN HAZ / WEN / DEN en-lol

Scenario outlines

  Scenario: Regular numbers
    Given I have entered <a number> into the calculator
    And I have entered <another number> into the calculator
    When I press divide
    Then the result should be <result> on the screen

  Examples:
    | a number | another number | result |
    |   12     |        5       |   7    |
    |   20     |        5       |   15   |
  

Background

  Background:
    Given a global administrator named "Greg"
    And a blog named "Greg's anti-tax rants"
    And a customer named "Dr. Bill"
    And a blog named "Expensive Therapy" owned by "Dr. Bill"

  Scenario: Dr. Bill posts to his own blog
    Given I am logged in as Dr. Bill
    When I try to post to "Expensive Therapy"
    Then I should see "Your article was published."
  

Steps

• Glue scenario to test subject
• Written in Ruby (but also Python, Java, Groovy, Scala, Clojure, ...)
• Allow to interface to any system

Step definition

Given I have entered 3 feature

Given /I have entered (\d+)/ do |number|
    ## Some ruby code 
end step
    

Cucumber will spot:

• Undefined steps
• Ambiguous steps
• Redundant steps
• ... and propose steps when they are missing.

Screen output

Example of Test Subjects

• Web Application
• Command line application
• APIs (REST, SOAP, ...)
• …

(short) Demo time

Outside/In Dev

• Write a feature / make it pass / refactor
• The feature becomes the test
• Behavior Driven Development

UAT

• Validates the user expectations
• Expectations are captured in features
• We have our UAT base !

Production Monitoring

• Write feature describing the behavior of your application
• Run it on your production
• Output the results in a Nagios instance

Features

+

Screenshots

+

Custom formatter

=

User documentation !

Feature Life Cycle

• Requirements
• Development
• Regression testing
• Production

Cucumber

• Simple
• Powerfull
• Ubiquitous

Cucumber, c'est bon, mangez-en !