We religiously use BDD for user stories, it makes stories and acceptance criteria very hard to misinterpret. I used BDD for 3 years in a previous job, and was opinionated that it was the best thing in the world until I learned better. Today I believe doesn't fit the modern way to develop tests. Always look for opportunities to tweak what test is already existing as opposed to writing partially duplicated tests for new specs. The reason Cucumber / Gherkin / BDD is not great is this duplication; if every feature was mapped to a spec, there would be much duplication between the specs. What matters from a test perspective is the beginning state of a test; if reaching that state is common, then it is an opportunity for a test enhancement vs partial test duplication. At which point, the only caveat becomes the test duration for parallelization concerns. take a look at https://github.com/NoriSte/ui-testing-best-practices/blob/master/sections/advanced/test-states.md