Bdd using Cucumber

BDD using Cucumber
By Ashish Mishra

Confidential | Copyright © QAAgility Technologies Pvt Ltd
10 Sec Intro
Ashish Mishra
20+ years experience
Masters in Computer Science
Author of Selenium Book by McGrawHill
I am an Agilist!
@ash1shm

Ashish Mishra
QAAgility Technologies Pvt. Ltd. – Founder Director
M.S. Computer Science, Stevens Institute of Technology, USA; PG Certificate in Business Management from City University of NY (CUNY); B.E. CSE, Marathwada University.
Certified Trainer for Agile Testing, Certified Scrum Master, Expertise in Account management, application delivery and business analysis
20+ years of IT Industry experience with:
Larsen & Toubro Infotech Ltd, India
JPMorgan, India
Chase Manhattan Bank, USA
IBM, USA
Prudential Insurance, USA
Seasoned techno-functional entrepreneur with a track record of exhibiting innovative thought leadership, being self-driven, exceeding expectations and applying high standards. He belongs to the group of respectable innovators in the area of processes consulting & automation testing. He is the executive member of the Indian Testing Board (ITB) and founder of the Agile Testing Alliance (ATA).
Experience in software testing, development, corporate training and public domain training. Over the period he has worked on number of projects as Account Manager, Test Manager, Programmer and Tester. His core expertise lies in Manual Testing, Test Automation and Test Management.
Capital Markets related technology projects in delivering e2e mid to large size projects in the area of application development, re- engineering, process consulting and QA. Worked with clients spread across the globe, USA, UK, Germany, China, Singapore, Australia and Japan.
Published author of the book "A Practitioner's Guide To Test Automation Using Selenium" by Tata McGraw-Hill.

Tools Never Solve Problems
•Fool with a tool is still a fool
•Use right tool for the right problem

Goal
•Introduce Cucumber tool for Behavioral Driven Development

What is BDD
•Hint: It is not about Test Automation

Software – What can go wrong?
•Implementation Defects
•Requirement Defects

Facts
•50-60% of issues identified by testers can be linked to Requirement Defects
•100-200% expensive to fix than other defects because the code is already written

Requirements – often misunderstood

Scrum
US 1 and 2
US 3
US 1 ,2 ,3

BDD
Business
•Domain driven design
Technology
•Test driven development

describe the
behavior
of your software
in a very understandable
way

Cucumber is Ruby-based BDD framework

What about Java?
Java: Cucumber-JVM
•Released in April 2012
•Pure Java
•Supports: Java, JavaScript, JRuby, Scala, Python, Groovy, Jython and JRuby

1 Describe Behaviour
2 Write step definition
3 Run and fail
4 Write code to make step pass
5 Run and pass

Writing Scenario's in Cucumber
•Scenarios are organized together into features
•Each feature is represented as a plain text file.
•Feature files must have the “.feature” extension
•Each feature can contain many scenarios

Behavior
Feature: <short description>
<story>
<scenario 1>
<scenario n>
WHO? As a <role> WHAT? I want <feature> WHY? so that <business value>
Scenario: <description>
Given <preconditions, context>
[And] <additional preconditions>
When <action, behaviour>
Then <postconditions>
[And] <additional postconditions>

BDD Feature
Feature: Depositing money in to a User account
Scenario: Depositing money in to User's account should add money to the User's current balance
Given a User has valid bank account
And a User has $X money in their account
When $Y is deposited in to the account
Then the balance should be $(X+Y)
This is Gherkin

Gherkin
Gherkin is the language that Cucumber understands. It is a Business Readable, Domain Specific Language that lets you describe software’s behavior without detailing how that behavior is implemented.
•Easy to read
•Easy to understand
•Easy to discuss
•Easy to parse

How does BDD help?
•All stakeholders involve in discussion
•Specifications having acceptance tests built into them
•As the software evolve the tests also updated
•Specifications are about how the system should behave in various scenarios

User Story and Scenario
Title (one line describing the story)
Narrative:
As a [role]
I want [feature]
So that [benefit]
Acceptance Criteria: (presented as Scenarios)
Scenario 1: Title
Given [context]
And [some more context]...
When [event]
Then [outcome]
And [another outcome]...

Scenarios
Story: Account Holder withdraws cash
As an Account Holder
I want to withdraw cash from an ATM
So that I can get money when the bank is closed
Scenario 1: Account has sufficient funds
Given the account balance is $100
And the card is valid
And the machine contains enough money
When the Account Holder requests $20
Then the ATM should dispense $20
And the account balance should be $80
And the card should be returned
Scenario 2: Account has insufficient funds
Given the account balance is $10
And the card is valid
And the machine contains enough money
Then the ATM should not dispense any money
And the ATM should say there are insufficient funds
And the account balance should be $20
And the card should be returned
Scenario 3: Card has been disabled
Given the card is disabled
Then the ATM should retain the card
And the ATM should say the card has been retained
Scenario 4: The ATM has insufficient funds
...

Group Exercise
•Read the ATA SSC Vision document and the user stories and write the Features in Given- When-Then format

Attributes of Good Feature document
•Complete
•Testable
•Specific

Thank You.
ashish.mishra@qaagility.com
in.linkedin.com/in/ash1shm/
www.agiletestingalliance.org
www.qaagility.com

Bdd using Cucumber

Recomendados

Recomendados

Más contenido relacionado

Similar a Bdd using Cucumber

Similar a Bdd using Cucumber (20)

Más de Agile Testing Alliance

Más de Agile Testing Alliance (20)

Último

Último (20)

Bdd using Cucumber