A couple years ago I used Cucumber on one project and wrote all the acceptance tests with it. That was a fair bit of work and I’d say even fun to start with when writing them initially.
However, something eventually started to feel off about writing those Cucumber specs, even after using a page model to DRY them up.
In the end, for me, the time spent writing the glue code between the plain English specs and driving the UI just wasn’t worth the trade-off in that particular project. No non-developers needed to read the specs so the benefit of Cucumber in that regard was of no use. RSpec or Rails’ TestCases would’ve been a better choice.
Even if a non-dev had to read them, non-Cucumber acceptance tests can be written to be readable to non-devs with a little training and a helping hand to start with.
Perhaps try Cucumber out for yourself on a branch or write a small scaffolded app so you can make your own call on it.