DenkzeitWiki

Main /

Behavior Driven Design

Agile
TestDriven
It's not about testing - it's about design - specifying behaviour.
Testing a Unit -> Observing Behaviour

---

• http://en.wikipedia.org/wiki/Behavior_Driven_Development
  
• http://behaviour-driven.org/

Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning.

• http://dannorth.net/introducing-bdd
  
• A NEW LOOK AT TEST-DRIVEN DEVELOPMENT
  • http://techblog.daveastels.com/2005/01/12/one-assertion-per-test/
    • The key is that instead of using a single TestCase? subclass with a complex (i.e. multiple assertion) tests for each situation, we made each of those situations into a separate fixture. Each fixture is implemented by a separate subclass of TestCase?. Now each test focuses on a very small, specific aspect of that particular fixture.

---

• Beyond Test Driven Development: Behaviour Driven Development
  • don't test state - observe behaviour (don't use reflection to get state of private fields)
    • use mocks!

BDD with VS

• http://blogs.msdn.com/elee/archive/2009/01/20/bdd-with-mstest.aspx
• http://www.codeproject.com/KB/library/GettingStartedWithBDD.aspx