• 1. Sogeti
  • 2. JBoss
  • 3. IBM
  • 4. Oracle
  • 5. SpringSource
  • 6. NL-JUG
  • 7. Java


Syndication  RSS 2.0

RSS 1.0
RSS 2.0

Bookmark this site

Add 'JCN Blog' site to delicious  Add 'JCN Blog' site to technorati  Add 'JCN Blog' site to digg  Add 'JCN Blog' site to dzone

Posted by Jan-Hendrik Kuperus at 23:55 on Monday 15 March    Add '/dev/brainst||m – Behavior Driven Development' site to delicious  Add '/dev/brainst||m – Behavior Driven Development' site to technorati  Add '/dev/brainst||m – Behavior Driven Development' site to digg  Add '/dev/brainst||m – Behavior Driven Development' site to dzone

On our most recent installment of a /dev/brainst||m meeting, we took a dive into Behavior Driven Development. Our colleague Maarten van Berkel uses BDD at his client’s project to facilitate better development and better testing of their Ruby software.

Behavior Driven Development (BDD) is a method for developing software much like Test Driven Development (TDD). Both methods start development with specifying test cases for a feature. The big difference lies in the way these tests are defined. TDD generally defines its scenarios in unit tests expressed in some programming language. BDD lets you specify your test scenario’s in plain English (or Dutch, or whatever). This forces you to think in working features over working units of code.

Read the rest of this entry »

© 2020 Java Competence Network. All Rights Reserved.