3 ms·
I think there's a lot of people down on cucumber after experience with it, in several different contexts... what do you think, what has been your experience?
by jrochkind1 8y ago
I think there's a lot of people down on cucumber after experience with it, in several different contexts... what do you think, what has been your experience?
- maxxxxx 8y agoWe tried it for a little and concluded that it made nothing really better but a lot of things worse. We just should accept that a tester needs to learn writing code. I wish it were different but Cucumber is not a solution.
- rhinoceraptor 8y agoI once was tasked with writing a script to generate the cucumber implementation boilerplate, from the cucumber tests themselves. Because the tester would constantly mess it up if he did it manually. Needless to say, it wasted a ton of time and never produced any meaningful value.
- jrochkind1 8y agoDid you verify the functionality of your cucumber-implementation-generating code with cucumber? :)
- Macha 8y agoThe dream of having the requirements be the test is not realistic: * Good luck telling your PM their English has a syntax error * Once that's out the window and the cucumber files are just maintained by devs, is the regex translation layer worth it? * A lot of implicit state also gets wrapped up in the test in making these phrases at least semi-readable, which makes for a pain debugging failures.
- rhinoceraptor 8y agoYou can also enter Cucumber-developer double jeopardy where you need to meet with the PM for an hour to write Cucumber specs, and then meet with the QA for an hour to implement them. When you could have just written a simple integration test in 15 minutes, but the Scrum master thought Cucumber would be a good idea.