LEARNING TDD/BDD

Session 4 - Acceptance Testing

Presented by Guyllaume Cardinal for Cogeco Connexion

What we've seen so far

Basics

TDD vs BDD

Benefits of TDD

Coding principles: SOLID, GRASP Single Responsability principle

Code smells

What we've seen so far

Unit Tests

Tests a single unit (class)

Focus on behavior

Mocks are used to isolate what is being tested

What we've seen so far

Integration Tests

Test a feature

Multiple classes interact together

Use abstractions to remove binding to web services and databases

Testing Pyramid

We are now in "user land"

How developers imagine users:

Acceptance tests are basically a user (or a QA person) visiting and interacting with your website and expecting certain things

gIVEN - wHEN - tHEN

The Given-When-Then formula is a template intended to guide the writing of acceptance tests for a User Story:

• Given some context
• When some action is carried out
• Then a particular set of observable consequences should happen

gIVEN - wHEN - tHEN

Feature: Serve coffee
  In order to earn money
  Customers should be able to
  buy coffee at all times

  Scenario: Buy last coffee
    Given there are "1" coffees left in the machine
    And I have deposited "1" dollar
    When I press the "coffee" button
    Then I should be served a coffee

Where's the code?

Scenario: I download a file
  Given I am in a directory "/foo"

<?php
class FeatureContext extends BehatContext
{
    /**
     * @Given /^I am in a directory "([^"]*)"$/
     */
    public function iAmInADirectory($dir)
    {
        if (!file_exists($dir)) {
            mkdir($dir);
        }
        chdir($dir);
    }
}

Writen in plain english (most of the time)

Okay, but hold on. Why english?

Behat report

WARNING!

What to test?

Our full testing Stack

Unit:

Integration:

Acceptance:

Test each class individually

Test that the app behaves like the user expects it to

REal world example

cogeco.ca