Hi Thomas,
Sadly, what you have said is 100% true.
Often companies give to QA the responsibility about BDD, but that is an awful idea. QA does not know about BDD, and they use Gherkin as pure scripting languages, which lose all of its benefits. About this just three weeks I wrote this article:
And really some time ago I wrote this other one:
Often people confuse both, and they should not.
Doing BDD right is hard, but not as hard as it seems. Unfortunately, I do not why, most of the manuals about BDD adoption focus on QA. BDD is not about QA. It is about the developers. That gave me a new insight, which tested positively, and I wrote this other article about it:
Summing up, it may seem a kind of obvious, but BDD is:
Behaviour Driven Development
not BDT:
Behaviour Driven Testing (or Quality)
although it often seems QAG:
QA with Gherkin
Thomas, thank you so much for your contribution. I hope others to read it and realize that BDD is something that has to be taken seriously, not just a toy for QA people.
BTW: There are alternatives for BDD to achieve the same objective. XP focus on that, for example.
And BTW: I have the feeling that applying that metric in systems that rely on QAG instead of BDD may help to fix it (but I could not test it for enough time) (Thanks again!)
