I think that my effort is more focused around BDD-as-evolution-of-TDD, a lot of my focus is around language. Trying to create a framework that is not obtrusive, but rather foster people to think in terms of the behavior /specification/functionality of the class they are trying to test-drive. For example my framework attributes is Functionality (TestFixture) and Specification (Test) to annotate the class and methods.

I have found that developers new to TDD normally make all the usual mistakes and then loose faith in TDD. So take away the Test idiom and suddenly people think in terms of behavior and specification. Hopefully helping them to write better tests (specifications :-)…

When are we going to see information surrounding the ideas behind jBehave and how to use it, etc…?

The main differences between the xBehave (JBehave, NBehave) and xspec (rspec, sspec) families are:

• xspec uses the vocabulary of “specification” where xBehave talks about “behaviours”.
• xspec is exclusively looking at BDD-as-evolution-of-TDD, whereas xBehave is also about automating stories and scenarios.
• xspec extends the language to add DSL-type verification, so it is well-suited to dynamic languages (Ruby and Smalltalk are the current target platforms). xBehave uses Joe Walnes’s constraints-based approach.

I’ll be releasing rbehave 0.1 just as soon as I can work out how to roll a Gem :)

I see TDD as performing the following roles:

1. Design process
2. Requirements Capturing
3. Behavior Specification
4. Regression Test Suite

For this reason I think we need a Behavior-Driven Development framework.

My daily development environment is .NET and C#, thus I would like to have something that suites my needs. Dave is working on rSpec for RoR and then there is JBehave for java. But I was unable to find anything for the .NET space. So I thought, I will roll my own.

Here is what I have so far:

using NBehave;

namespace SampleBehaviour
{
[ Functionality ]
public class CustomerLoadBehaviour
{
private Customer customer = null;

[InitializeSpecification()]
public void Setup()
{
customer = new Customer(123);
}
[ Specification() ]
public void ShouldLoadCustomer()
{
Behaviour.Of( customer.Id ).Must.Not.Be.Null( “The Customer Id must not be null.” );
Behaviour.Of( customer.Id ).Must.Equal( 123, “The customer id’s aren’t equal” );
}
[ Specification() ]
public void LoadCustomerShouldFailed()
{
Behaviour.Of(customer.Id).Must.Not.Be.Null(“The Customer Id must not be null.”);
Behaviour.Of( customer.Id ).Must.Not.Equal( 125, “The customer id’s aren’t equal” );
}
}
}

I’m busy working on a TestTip for VS2005, but have finished the NUnit integration.