5 ms·
What I understood is: You are supposed to capture requirements in Given/When/Then form before coding, and they should be written in a way that is independent o
by anentropic 8y ago
What I understood is:
You are supposed to capture requirements in Given/When/Then form before coding, and they should be written in a way that is independent of the implementation
The complaint seems to be that what happens in practice is "the devs have taken over" the system, so Cucumber just becomes a test automation software
This has led to writing tests in Given/When/Then format which test overly specific elements of the implementation, and are often written after the fact, instead of as a way to capture requirements.
And some other stuff, but that's primarily what I got out of it.
- tannhaeuser 8y ago> the devs have taken over [authoring tests] That's what happened in the projects where I used fitnesse, jbehave, cucumber, etc. The users couldn't understand the artifacts and what they're supposed to do, and the tools were highly idiosyncratic. It ended in becoming just yet another hassle for developers.
- pcm191 8y agoExactly. Whereas using Excel for specification of calculations (by Business Users or Business Analysts) actually brings the business and developers closer together, removing the need for intermediaries. Business Users are very happy using Excel and checking calculations etc. as it tends to be their home environment.