3 ms·

I've had, I think, 1 working experience and 6 or so highly negative and it was mostly the nature of the system under of test that made it work or fail. For sim

I've had, I think, 1 working experience and 6 or so highly negative and it was mostly the nature of the system under of test that made it work or fail. For simple and very clear Given/When/Then scenarios with clear inputs and results that were easily represented with a small amount of text it worked. Think a trading system with a few codes and a small amount of data on the left and an expected result like a calculation on the right. Where there was a lot of stories that branched off from one another (e.g. a website with lots of potential user flows) it inevitably led to stories that were too vague or too repetitive or more usually, both. I'm convinced that it does work for a certain kind of application for which the DSL is capable of representing its scenarios, but it's not the kind most of us develop.

jaggederest 3y ago
The cases I was using it for involved internal applications, so you're right, there was a lot more clarity about "what to do when user click button b" than random people on the internet bouncing around a store and adding things to a cart. There were also a lot of cucumber scenarios and suites involved. Like think dozens of printed pages in relatively small font. Concise it is not. But the people involved wanted verbose and clear over concise and easy :) It can be a very reassuring way to develop software for stakeholders - "We added 8 scenarios, and made a further 4 failing scenarios pass this week" - as opposed to "our developers spent 6 months and then quit without delivering any code"