|
|
|
|
|
by nickjj
1199 days ago
|
|
I've never seen Cucumber used in a big project after having done contract work for a long time but the idea of having user stories defined in a systematic way that's only used as extra context / documentation for complex features is useful. That would be aimed at developers and it would live near the real test code so it's not necessarily a direct implementation of how Cucumber is intended. For more basic things it's overkill, certain languages almost give you the same benefit with code itself. For example, here's a real user sign in controller test from Rails: test "doesn't send email for an unknown user" do
post sign_in_path, params: { email: "idontexist@example.com" }
assert_enqueued_emails 0
assert flash[:alert]
assert_response :unprocessable_entity
end
You don't need to know Ruby or Rails to have a good idea of what's happening there. |
|