1.
Behavior Driven Tes.ng (BDT) in Agile

2.
What is Tes*ng on Agile projects?

3.
Story planning and wri/ng Showcase IPM Automa/on (execu/on, QA kickoff maintenance) Agile Tes.ng in an Itera.on Manual + Exploratory Story kickoff Tes/ng BA / QA Test Scenario Volleyball Wri/ng Implement Test Automa/on

4.
A prac*ce that makes Agile Teams successful? Test Automa.on

5.
A prac*ce that makes Agile Teams unsuccessful? Test Automa.on

6.
The Test Pyramid • “Succeeding with Agile” – Mike Cohn • Mar*n Fowler – Test Pyramid – hCp://mar*nfowler.com/bliki/TestPyramid.html

7.
Ideal Test Pyramid Func/onal Tests (GUI) • Developers & / QA team API Tests • Developers & / QA team Integra/on tests • Developers Component tests • Developers Unit Tests • Developers Cost / Effort Time

8.
Test Pyramid reality Development team Test Pyramid QA team Test Pyramid

9.
Test Pyramid – An* PaCern

10.
Evolu*on of Test Frameworks Behavior Driven Development (BDD) Op/mized scripts Record & Playback Core Framework

11.
Behavior Driven Development (BDD)

12.
RED REFACTOR GREEN

13.
Behavior Driven Tes*ng (BDT)

14.
Expected Func/onality: The customer should be able to withdraw money from his account via an ATM machine

15.
BDD Example: Given the account has balance of 5000 When the customer requests 1000 Then the account is debited by 1000

16.
BDT Example: Given the account is in credit And the dispenser contains cash When the customer requests cash Then ensure the account is debited And ensure cash is dispensed And ensure the card is returned

17.
New Expected Func/onality: The customer should be able to withdraw money from his account only if his card is valid

18.
BDT Example -­‐ updated: Given the account is in credit And the card is valid And the dispenser contains cash When the customer requests cash Then ensure the account is debited And ensure cash is dispensed And ensure the card is returned

19.
Case Study

20.
Requirements • Guest User is able to search for a flight for a single traveller • Ability to specify contact informa*on for person booking the flight

21.
Search Contact Search Results Informa/on

22.
Contact Details

23.
Test specifica*on styles • Impera*ve • Declara*ve

24.
Impera*ve style Given I am a guest user on the Indigo home page And I select “round” trip op*on And I select “Pune” from the origin dropdown And I select “Bangalore” from the des*na*on drop down And I select departure date as “5 July 2012” And I select returning date as “25 July 2012” When I click on Search Then I should see the search results page And I should see at least 1 op*on for my criteria ...

25.
… When I select the “first” op*on Then I am on the Contact Informa*on page When I enter first name as “foo” And I enter last name as “bar” … … And I click the “Select and Con/nue” buCon Then I should be on the next page

26.
Declara*ve style Given I am a guest user When I search for flight op*ons for a “one-­‐way” trip for “1” “Adult” from “Delhi” to “Bangalore” And I select the “first” flight And I enter “valid” contact details for “traveller1” Then I am able to Save and Con*nue

27.
Func/onal Tests (GUI) • Developers & / QA team API Tests • Developers & / QA team Integra/on tests • Developers Component tests • Developers Unit Tests • Developers

28.
What does BDT do for me?

29.
What BDT does NOT do for me? • Replace tes*ng granular func*onality – ONLY when it has just been developed

30.
Steps to follow to implement BDT

31.
Current state Tests running on Hudson / Jenkins Since 1st test was automated Feature files 33 Scenarios 65 Smoke tests execu*on *me 15 minutes Regression tests execu*on *me 45 minutes Test case repository (manual + Cucumber .feature files with automated) appropriate tagging Project Management tool Mingle

32.
Tools to enable BDD / BDT • Cucumber • JBehave • SpecFlow • Twist

33.
Anand.Bagmar@thoughtworks.com abagmar@gmail.com ThoughtWorks®