Feature / integration / acceptance spec styles

[thehenster]

A community styleguide for feature specs (capybara / rails) would be useful, as well more general guidance for longer acceptance / integration tests.

For example..

Should a large acceptance test describe everything it hopes to prove in a multiline example description? Or should we favour a shorter description with comments to tell the story (if required)?

# GOOD
scenario "A user is created, " \
         "a welcome email is sent, " \
         "and they are shown their dashboard"
  ...
end

# BAD
scenario "User signup" do
  # A user is created
  ...
  # A welcome email is sent
  ...
  # They are shown their dashboard
  ...
end

My question is more about whether betterspecs should be talking about acceptance specs, rather than the above example.

[thehenster]

I found http://rubocop-rspec.readthedocs.io/en/latest/cops_capybara/. While capybara specific, it does seem like the type of thing I was talking about.

[akz92]

I like that! Feature tests are (or IMO should be) an important part of an application's test suite. Would you like to start this? And then maybe we could open it for discussion once we have something to talk about.