A list of best practices used by mature development teams. In the form of "Quiz" - you can point which of them you use and answer how advanced your team is.

How does BDD compare with TDD, and how can you use BDD-style tools such as Cucumber and SpecFlow with ASP.NET MVC? Steve Sanderson considers the options, and provides an example of combining ASP.NET MVC 2, SpecFlow, and WatiN.

A low friction approach to get rolling with TDD/BDD.

have you hand-rolled your own base class for your Context/Specification style specs? Curious whats different between a Context/Specification base class and a typical unit testing base class? read on...

The purpose of this post is to run through a process which will ultimately allow you to write Ruby based specifications for your .NET code. Why would you want to do this? The intended purpose for this practice is to gain the most benefit when doing BDD. Trying to do BDD in C# results in a lot of syn...

As developers start to discover the upcoming Code Contracts for .NET 4.0, it's important to understand not only Design by Contract, and TDD, but how they can complement each other. For business value, we as developers need to flush out our design through the use of TDD, and we can refactor into usi...

"How-to" example of TDD / BDD

Ayende proposed a new AAA syntax in Rhino Mocks. I was wondering how it mixed with BDD.

I really like the look of my tests specifications, they read almost like plain English. After fumbling around for a while, I finally get how to specify an expected exception.

Basically it a shift towards specifying behavior instead of testing behavior. The specification consists of 3 parts: 1: A namespace with called "Specs_for_subject" 2: One or more classes called "When_operation_on_state", with a SetUp/Init method that performs the "op...

Using a bdd_style_naming_convention_for_you_specifications? Save yourself some time and keystrokes by using BDD AutoHotKey Script.

Second part of an article about BDD (Behaviour Driven Development).

A little app to turn BDD tests/specs into a non-developer readable text document.

"Test Supported Development" (TSD) intends to characterize the creation of tests during ANY/ALL stages of development, that is, tests are not necessarily created before their respective System Under Test (SUT), but not necessarily created as an afterthought, either...