Rspec vs. cucumber user story function

Question

Just to be in front, although the name seems to be similar to the RSpec vs Cucumber (RSpec stories) stream, however my question is fundamentally different.

I understand the difference between testing user stories and testing the behavior of objects separately. My question is why is Cucumber usually associated with RSpec for writing user stories when RSpec has user story functionality since 1.1? Is this because RSpec's focus remains strong on individual object testing, and has Cucumber been actively developing since then with an emphasis on user history?

Context switching is a pain, and we, the developers, are dealing with sufficient tools. I would prefer to stick only to RSpec, but if there are any important differences that Cucumber is from RSpec, please let me know.

Answer 1

The difference is quite simple: the cucumber is Runner Running. Or rather, Cucumber is Runner Running.

So, the cucumber is supported, the Runner Runner RSpec is not. Runner Runner obsolete and obsolete, no cucumbers. Cucumber is still developing, Runner Runner RSpec is not. The upcoming RSpec release no longer contains (and does not support) Story Runner.

The fact that RBehave (a preliminary cucumber pointer) was combined with RSpec was a purely historical disaster and should never have been done in the first place. That's why pretty soon after the merger, the companion RSpec Story Runner declared him dead and wrote Cucumber.