Hacker News Reader

Comment by wreegab | Hacker News Reader

It's nice when acronyms, such as "TDD" and "BDD" here, are expanded at least once in the text when they first occur -- I don't think it would put a lot of burden on writers. There is too much of these insider knowledge acronyms all over the internet nowadays.

Anyways... I gather "TDD" means "Test-Driven Development" and "BDD" means "Behavior-Driven Development".

View on HN

What the hell is behaviour driven development? Everyone has some sort of behaviour, so it sounds as if everyone must be practising it.

Recently I spotted a new one, domain driven development. I decided to read up on it and realised this is how I had been taught to design code, and how I generally go about doing things. Its got a name now.

I have explained Behavior Driven Development and its benefits here http://www.mehdi-khalili.com/bdd-to-the-rescue.

Hope it helps.

Thanks for that but to be honest it just sound like more of the same, but viewed from a different angle.

My understanding of your write up is that that tests may be written without understanding the problem. I mean that is just dumb TDD religious zealots who would do that sort of thing, assuming that test make up for design (and thought process). I also think that the verification process is an inherent part of waterfall model - hence the iterations.

Test driven development with silly/vague method names, like it() and should(), often written by people who don't write the code so behaviour can be defined separately from implementation.

It was quite popular in the ruby community a couple of years ago.

Fair comment. I actually do that very often (e.g. CI and CD in http://www.mehdi-khalili.com/continuous-integration-delivery...).

I guess the reason I didn't do it for BDD was that I have written a lot of posts about Behavior/Test Driven Development and incorrectly assumed that my readers know about that. My mistake. It's fixed now. Thanks.

Reply on news.ycombinator.com