&gt; If you&#x27;re using it to communicate features to other team members, it can be super-useful, since it&#x27;s much easier to comprehend that the equivalent developer-friendly code.<p>In ruby&#x2F;rspec it&#x27;s actually still understandable and direct. in other languages, maybe not so much.<p>I have not run into a cucumber implementation I liked. I agree it can lead to a human readable spec, but the effort it takes to get there, and stay there, is a nontrivial cost in terms of maintenance&#x2F;flow&#x2F;optimization. I don&#x27;t think it solves technical problems, but organizational.<p>It&#x27;s all about tradeoffs, with everything we do. Outside of someone else writing and maintaining the spec, I don&#x27;t think the downfalls at all warrant any benefit of clarity.<p>cucumber is not &quot;free&quot; to use, it&#x27;s a commitment with lots of fine print. I suppose thats really what i&#x27;m trying to advocate, in the end. At least thats been my experience across 5 or so projects with it. YMMV.