Admittedly, I never dealt with Cucumber.
* It's verbose.
* It's not type safe.
* It desperately needs some kind of inheritance - most user stories branch from other user stories (e.g. put product in shopping cart->purchase product) and the only way people who use it can deal with it is by concealing critical details in code or by writing massively repetitive stories.
* What other language has a parser that routinely asks you to write regexes to get things to parse?
None of these things are fixable and the creators have largely reacted to the complaints with gaslighting: "you're just using it wrong".
It can be used effectively if you align the stars correctly but mostly not.
The one thing it does get right is not being turing complete - there's clear value in not using code to describe scenarios.
I wouldn't lump RSpec in with the rest of those.
Spec-style frameworks (like granddaddy RSpec) are terser. They don't have layers of indirection. They're intended to help devs think about how code will be used, not to make code look like English.
Cucumber mostly exists to upsell naive MBAs and project managers on their "pro" tools.
i know that 99% is badly written sure.
but bdd cucumber style testing if done right can be good. problem i saw people just incapable.
I don’t mind it if you use cucumber and it still serves the purpose of describing your code’s behaviour, so the output is readable. RSpec’s documentation is a nice example of that.
The problem is if people just use it as a syntax over a webdriver, which means that your test behaviour and logic is arbitrarily split into two different languages, the cucumber output is useless, the tests are needlessly slow, and it’s really hard to debug. Cucumber itself is not able to add value there.
But that’s not unique to cucumber either. I don’t think many people realise that test writing and architecture is its own skill in programming and so many suites turn into write-only cludges that take 12 hours to run on a cluster of 50 CI workers.
Cucumber and WebDriver? Two problematic frameworks does not equal a sane one.
Found it quite neutral, not too bad, but also not really helpful.. some nice ideas especially that cross functional collaboration, but in the end the engineers had overhead and hated to write the wrappers, and the other stakeholders still couldn't or didn't want to read/write docs/test, or however it was intended. Admitted, maybe I belong to that incapable crowd as well ;)