10 likes
路
232 reads
3 comments
Great post Sean. 馃憦
When I first met BDD I imediatell fell in love with it.
Nowadays I am not using BDD as it adds one extra layer of complexity which result in a much higher maintenance cost.
One of the biggest USP of BDD is that managers can understand it too. In reality they will never check it.
There is one exception: Karate DSL for API testing. Because you only have to write plain English(Gherkin) as all the requests and assertions are implemented in the framework itself. 馃槉
Hi Miki, thanks for the response!
The maintenance costs can be tough and I鈥檝e personally been involved in some grueling updates to broken Cucumber tests. It鈥檚 not an experience I鈥檇 recommend.
I think the way BDD makes you think about code is helpful. I believe even if you aren鈥檛 creating BDD tests it can still help you reason in a more effective way.
I totally agree with you Sean Coughlin.
I only wanted to write that you can have BDD style code without adding one extra layer of complexity. 馃槉