4 ms·

> but it wasn't something the stakeholders outside of engineering even wanted Ha this reminds me of the craze for BDD/Cucumber type testing. Don’t think I ever

• jaggederest 3y ago
  I've used Cucumber on a few consulting projects I've done and had management / C-level interested and involved. It's a pretty narrow niche, but they were definitely enthusiastic for the idea that we had a defined list of features that we could print out (!!) as green or red for the current release. They had some previous negative experiences with uncertainty about what "was working" in releases, and a pretty slapdash process before I came on board, so it was an important trust building tool.
  • jamiek88 3y ago
    > important trust building tool This is so often completely missed in these conversations about these tools. Great point.
  • btown 3y ago
    “Incentivize developers to write externally understandable release notes” is an underrated feature of behavioral testing frameworks!
• hitchstory 3y ago
  Ive had product owners take an interest in docs autogenerated from tests. Especially with artrfacts embedded. They like tuff like this: https://github.com/hitchdev/hitchstory/blob/master/examples/website/docs/add-and-retrieve-todo.md https://github.com/hitchdev/hitchstory/blob/master/examples/... And can be persuaded to look at the (YAML) source. Gherkin isnt really a suitable language for writing test cases in - it's verbose, lacks inheritance, has clunky syntax and is stringly typed.