Okay, let me get something straight… for the past several MONTHS I’ve been trying as much as possible to distill my thoughts on Behavior Driven Development and each time I tried I wound up with a train wreck of a blog post that I would promptly delete. While commuting to work today I finally realized why I kept having so much trouble: I was trying to cover too much in one post.

Therefore this is simply going to serve as an introductory post for several small posts that describe my philosophy around different aspects of BDD and most of my practices that grew naturally through several years of experience developing software test first. A lot of emphasis will be on switching focus from “Test Everything That Can Possibly Break” to “Describe How This System Should Work.”

In the days and weeks to come, you’ll definitely see a variety of posts detailing my experiences that led me to a BDD mindset and I hope to use each post to describe each aspect of BDD in high detail. I’ll update this post with links to each successive post for future reference.

  1. From Acceptance Tests To Story Level Specifications

Cheers! ;)

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • BlogMemes
  • Blogosphere News
  • description
  • Fark
  • LinkedIn
  • NewsVine
  • StumbleUpon
  • Technorati
  • TwitThis
  • Yahoo! Buzz

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!