Comments on Andrzej on Software: What do I gain from TDD or BDD?

@tomfmason,Thanks for your response.I'm interested...

2008-01-31T01:53:00.000+01:00

@tomfmason,

Thanks for your response.

I'm interested in your experience with PySpec. One of the projects I'm working on is Python-based. Is it stable enough to start using it?

Did you start with BDD without actually knowing TDD?

RSpec's is easy, indeed.

@andrzejI am using rspec mostly. I have also worke...

2008-01-31T00:51:00.000+01:00

@andrzej

I am using rspec mostly. I have also worked with phpspec and pyspec as well. However, I find that rspec's syntax is the easiest to work with.

When I first started the hardest part was understanding the general concept behind BDD. I was thrown into a large project with no BDD or Agile/Xp development experience.

It took me a few days and a lot of googling to understand the basic concept. The good news is that rspec's syntax is really easy to work with. Intermediate or higher level rails developers shouldn't have a problem once they get the concept behind BDD.

tomfmason:Thanks for your comment.Well, it takes s...

2008-01-30T01:00:00.000+01:00

tomfmason:

Thanks for your comment.

Well, it takes some time to learn, and is not really that intuitive when you start doing TDD or BDD. This is why I meant expensive or difficult.

Actually, I think that BDD might be easier than TDD, it's usually better organized.

As for pair programming, I find it a good way of teaching people doing BDD. You have more time to explain the philosophy behind it. Also you can show many details, and the "flow" of being driven.

What framework are you using for specs? RSpec?

I would have to disagree with you in that BDD is d...

2008-01-29T23:45:00.000+01:00

I would have to disagree with you in that BDD is difficult or expensive. There is a bit of a learning curve but after that it should be easy. The extra expense only comes in when working with inexperienced developers or using something like pair programming.

I write most of my specs for a user story before I write any actual spec code. This gives the team a chance to review it and make any adjustments. Applying the specs into spec code is basically a copy and paste operation after that.

Just seen your blog (link from DZone), nice work! ...

2008-01-24T01:44:00.000+01:00

Just seen your blog (link from DZone), nice work!
Pozdrowka z Catford!

jdm:One test is better than no tests. As you say, ...

2008-01-23T23:52:00.000+01:00

jdm:

One test is better than no tests.
As you say, it gives you better feeling how it works.

bewhite:

Comparing BDD to TDD? Yeah, it might be a good post for the future. Thanks for the hint!

I'm using TDD in the Rails project now but I would...

2008-01-23T21:17:00.000+01:00

I'm using TDD in the Rails project now but I would like to know more about BDD.

Can you compare these technics? When we should and when we shouldn't use each of them?

I understand that it is quite common question so maybe you can write another one post about it?

"The good news is that you can start introducing i...

2008-01-23T20:06:00.000+01:00

"The good news is that you can start introducing it gradually."

This is the one thing nobody ever told me. The TDD/BDD mantra is 'test everything,' which is paralyzing when you sit down to start a new project. By getting at a small piece of it, it's easier to see how things should work, and then you can apply it to other areas.