Skip to main content
6 events
when toggle format what by license comment
Jun 17, 2020 at 22:38 comment added Stanislav Bashkyrtsev He also refers to DDD's ubiquitous language as an inspiration for BDD, but BDD provides ubiquitous template (not language). And the whole idea of BDD is not universally accepted either.. BAs who write tons of extra lines just to easily automate tests, which most likely will be automated on the highest possible level (which in turn is bad for maintainability and performance) by people who aren't really able to write code (that wasn't a part of the ideology, but it turned out this way).. I like the idea of naming tests meaningfully, but that idea shouldn't have gotten further than that.
Jun 17, 2020 at 22:16 comment added Daniel It is worth noting that he makes some statements in the article about acceptance criteria that are not universally accepted. In particular, he states that acceptance criteria should be executable. As he has no claim to the term, that statement does not have more (or less) validity than other experts on the topic that would allow non-executable acceptance criteria.
Jun 17, 2020 at 22:12 history edited Daniel CC BY-SA 4.0
parts of my answer were factually inaccurate and I updated it to reflect my new knowledge.
Jun 17, 2020 at 22:09 comment added Daniel Thank you for the fact check. I stand corrected. I will adjust my answer accordingly.
Jun 17, 2020 at 21:40 comment added Stanislav Bashkyrtsev GWT format was not created for Acceptance Criteria - actually that's not true.. This format was created as a tool for collaboration of BAs, QAs and Developers. See dannorth.net/introducing-bdd: "we were trying to define a ubiquitous language for the analysis process itself!", and "The template had to be loose enough that it wouldn’t feel artificial or constraining to analysts but structured enough that we could break the story into its constituent fragments and automate them"
Jun 17, 2020 at 20:29 history answered Daniel CC BY-SA 4.0