InfoQ Homepage Behavior Driven Development Content on InfoQ
-
*-Driven* do not change anything
Michał Bartyzel challenges the need to master a *Driven* approach to be Software Professional. These might be: DDD, TDD, BDD, MDD or other frameworks. He maintains that they may be responsible for cognitive biases rather than playing a supporting role for broader and deeper skills.
-
Metrics-Driven Development
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.
-
Virtual Panel: Code-to-Test Ratios, TDD and BDD
In the last couple of months several online discussions took place about test first or test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked the opinion of BDD and TDD experts.
-
Feature Injection: three steps to success
Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.
-
Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection
In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.