As TDD is more of running junits(at a very unit level) and hence we focus very little in writing tests which check code as a functional unit.
BDD(behaviour-driven development) fills up this gap I think and is more closely aligned to developers way of thinking.
I see it more like an organized functional tests in code!
As such system work in unison and not just as a small unit. Hence a boundary has to be defined as to which all parts of the system should be tested and how based on time/money tradeoffs ?
Implementations of BDD for java: http://jbehave.org/
Implementations of BDD for groovy: Easyb
Reference: http://www.jroller.com/DhavalDalal/entry/preferring_bdd_over_tdd
BDD(behaviour-driven development) fills up this gap I think and is more closely aligned to developers way of thinking.
I see it more like an organized functional tests in code!
As such system work in unison and not just as a small unit. Hence a boundary has to be defined as to which all parts of the system should be tested and how based on time/money tradeoffs ?
Implementations of BDD for java: http://jbehave.org/
Implementations of BDD for groovy: Easyb
Reference: http://www.jroller.com/DhavalDalal/entry/preferring_bdd_over_tdd
No comments:
Post a Comment