34
How not to do BDD? Priyanka Bhasin @priyanka23

How Not To Do BDD

Embed Size (px)

Citation preview

Page 1: How Not To Do BDD

How not to doBDD?

Priyanka Bhasin@priyanka23

Page 2: How Not To Do BDD

Tester

Page 3: How Not To Do BDD

eXtreme Programming (XP)

    

•Pair Programming•Continuous Integration•Small releases•Simple design•Sustainable pace•Refactoring•Test Driven Development (TDD)

Page 4: How Not To Do BDD

TDD ≠ BDD

Page 5: How Not To Do BDD

TDD

Page 6: How Not To Do BDD

BDD

FAILINGBEHAVIOURAL

TEST

Page 7: How Not To Do BDD

Behaviour Driven Development

Behaviour-driven development is about implementing an application by describing its behaviour from the perspective of its stakeholders”

Page 8: How Not To Do BDD
Page 9: How Not To Do BDD

Core principles

Page 10: How Not To Do BDD

It’s all about behaviour

Page 11: How Not To Do BDD

It’s all about behaviour

Page 12: How Not To Do BDD

It’s all about behaviour

Page 13: How Not To Do BDD

Where is the business value

Page 14: How Not To Do BDD

Where is the business value

Page 15: How Not To Do BDD

Where is the business value

Page 16: How Not To Do BDD

The three amigosBusiness Analyst /

Product OwnerTester Developer

Page 17: How Not To Do BDD

Anti Patterns

Page 18: How Not To Do BDD

BDD is a silver bulletThe first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency.

Page 19: How Not To Do BDD

Automation over Conversation

Page 20: How Not To Do BDD

No business value

Page 21: How Not To Do BDD

No business value

Page 22: How Not To Do BDD

Higher level scripting Language

Page 23: How Not To Do BDD

Higher level scripting Language

Page 24: How Not To Do BDD

And I wait for 10 seconds

Page 25: How Not To Do BDD

Business Stakeholders interested

Page 26: How Not To Do BDD

Business not interested

Page 27: How Not To Do BDD

Business not interested

• They don’t care about testing• They don’t write specification

on their own

Page 28: How Not To Do BDD

The more details the better

Page 29: How Not To Do BDD

Or this

Page 30: How Not To Do BDD

Or this for the win

Page 31: How Not To Do BDD

• Shared Knowledge• Focused Effort• Make Safe changes• Living Documentation

Page 32: How Not To Do BDD

Key Takeaways• TDD ≠ BDD• Not a silver bullet• Hide details• Business value• Ubiquitous Language• It is not about automation but about

collaboration

Page 33: How Not To Do BDD

…those who learned to collaborate and improvise most effectively have prevailed.”

Charles Darwin

Page 34: How Not To Do BDD

Thank You

/in/priyankabhasin

@priyanka23