hello!

[Dan North]

Hi there.

Just wondering who else is in the group..?

Regards,
Dan

[Tim Haughton]

Hi Dan, the group is not active yet, not sure if there are any
members. I will probably try to direct traffic here from say the Yahoo
TDD list/XP list as and when.

When I get the documentation for NSpec done, I'll put a link in there
too. I'm guessing you might be better placed to start the membership
off :) You might want to post links to your BDD site and papers on
here as a starter.

Regards,

Tim Haughton

[Dan North]

Hi Tim.

Yes, I came across the group because I was about to create one with the same name!

I presented BDD at a couple of conferences last year and several people asked me whether there was a mailing list. It took me this long to getting round to setting one up.

I'd like to talk to you off-line about whether you'd be interested in getting nspec aligned with jbehave - primarily in terms of the vocabulary. I'm also talking to the rspec guys - I'm trying to gently move people from specification and context to behaviour.

Cheers,
Dan

[Ing Gustavo Andrés Brey]

Hi Tim/Dan,
I have also joint here because I wanted to create one with the same. Every day, after attend Dave Astels's google video, I work with TDD I can't stop thinking in BDD terms and try to change and extend XUnit to fit better with BDD.
It is so great to share idea with people like you Tim and Dan (your blog is on my Reader). I'm looking forward to discussing about BDD design technique.

I have been working with TDD/JUnit/JMock/Mocquer since beginning of 2005 and I have gave two conferences at my company for all South America  (Argentina, Chile, Venezuela, Ecuador, Uruguay, Comolombia, etc) about it. I work for IBM Argentina. I'm planning to one one about BDD this year.

Thanks,

--
Saludos,

----------------------------------------
Ing. Gustavo Andrés Brey
gus...@gmail.com
http://gabrey.blogspot.com
----------------------------------------

[Dan North]

Hi Ing.

That's great stuff! I'm planning to blog a lot more about BDD this year, and in particular about how to use BDD as a methodology "from the outside in", starting with defining acceptance criteria using stories and automated scenarios, and driving that into class-level behaviour using the jbehave core and mocking.

By making the scenarios self-describing, which jbehave does for free, this creates a fully self-documenting system that can continually verify itself. The roadmap post-1.0 is to create a round-trip editor, so that you write the scenarios in a text editor in English (or Spanish!) and it generates stubs for the Given, Event and Outcome classes. Because these are self-describing, you can re-render the documentation text whenever you like and it will always be up-to-date with the application.

Cheers,
Dan

[Tim Haughton]

On 02/01/07, Dan North <tast...@gmail.com> wrote:
> I'd like to talk to you off-line about whether you'd be interested in
> getting nspec aligned with jbehave - primarily in terms of the vocabulary.
> I'm also talking to the rspec guys - I'm trying to gently move people from
> specification and context to behaviour.

Dan, offline stuff can be sent to my gmail (timha...@gmail.com).

Tim