At a major broadcaster where I have been working we have invested heavily in BDD.
Dev’s are trained in it, the business promotes it, time is given to us to be able to focus on it. Even so, we have made many mistakes. Our Cucumber builds can take hours, tests get forgotten, are hard to maintain and break often. But having development specked out by well documented feature files that show visibility of test coverage is still important. We solved this by creating our own completely different BDD tool called “Should It?”
This is not bound by any particular platform and will work with any technology or programming language you choose to write your tests in. Richard is the co-creator of this tool and is keen to share how it can help make your BDD workflow more pain-free.