News for hackers. Stuff that matters.
Re:The Tragedy of Given-When-Then by philipodonnell on Tuesday April 16, 2019 @09:48AM (#19673537)
> The discussion helped me realise that Given-When-Then is as much of a hindrance in some contexts as it is a help in other contexts.

I like when authors express a strong viewpoint but then also include descriptions of circumstances where their viewpoint may not be applicable. This seems to be alluded in the above quote, but are there specific contexts where Given-When-Then _is_ helpful and the appropriate mechanism to document requirements?

Re:The Tragedy of Given-When-Then by rgoulter on Tuesday April 16, 2019 @12:14PM (#19674900)
I think rspec's Cucumber docs are fine. https://relishapp.com/rspec/rspec-expectations/v/3-8/docs/bu...

It's an executable specification, but it's also in a format which is readable. If not "documentation", then it's at least "small, verified examples".

I'd find a table of values less readable. I don't mind if a document like this is the output of running the tests themselves, though. (Obviously, the important details are "input program, expected output", which might not lead you to use Cucumber, but I think it's a fine use of Cucumber).