Converting a requirement into executable tests – BDT

- Ravinder

Agenda

Why BDT?

Gap..Gap..Gap

Cap the Gap!!

Seal the Gap!!

What is BDT?

Who are involved in BDT?

8

Exercise expectations

againstMatches to

Customer QADomain Expert Developer

How?

Timing to introduce BDD

10

Prerequisites of a Good Executable Requirement

• Understandable to developer

• Understandable to business

• Unambiguous

• Automated

• Run frequently

BDT as test strategy

12

It is an approach to testing. Works towards the BIG picture.

BDD Tools JBehave – Java annotations based,

Test frameworks agnostic Cuke4duke – Cucumber support for

JVM JDave – RSpec (Ruby) inspired, Mojo

2 & Hamcrest based beanSpec – Java based easyb – Java based, Specifications

written in Groovy instinct – BDD framework for Java,

providing annotations for contexts. Inspired by Rspec

BDoc - Extracts behaviour from unit tests

13

BDD Tools C – Cspec C++ – CppSpec, Spec-CPP .Net – NBehave, NSpecify, SpecFlow Groovy – GSpec, easyb, Cuke4Duke PHP – PHPSpec Python – Specipy Ruby – RSpec, Shoulda, Cucumber More…

14

JBehaveJBehave

15

16

Benefits for Dev Team

- Provides a medium to talk to non-tech people to agree on common agenda.

- More business facing testing during development

- An extension of TDD (Primarily a dev practice)

17

Benefits for Business

- Focus on "Are we building the right product"

- Aligning business needs with technological implementation

- Establishing shared understanding

- Better ROI

18

Thanks