turkan wrote in post #962094:
turkan wrote in post #962004:
Then that tells me that their stories are too verbose.
English language is verbose
You're right. I used the wrong word. That tells me that their stories
are too *complex*.
No, it really isn't. ERb is not going to camouflage poorly designed
views. Steak looks very much like that's its primary design goal:
making it easier to write excessively intrusive stories.
I would be very curious to see some sample Steak tests.
Steak is a very very thin wrapper around RSpec ... so the test are
nearly pure Ruby/RSpec (mostly by directly accessing the Capybara
Example (not from me):
Interesting. I like parts of it, but I think Steak is fundamentally
One of the big reasons to write Cucumber stories in natural language is
that it stops you thinking like a programmer -- Cucumber stories are
about user-facing functionality, not implementation. Steak, with its
Ruby syntax, completely destroys that difference. Its Ruby DSL is
clever, but there appears to be a great temptation to write RSpec
controller specs with nicer syntax -- which is really not what user
stories are about.
Have you actually used Cucumber?
Doesn't Capybara do all that regardless?
Nope, from the Capybara README.rdoc: "The visit method only takes a
single parameter, the request method is always GET."
GET is all you need. If you want POST, you should be having the
Capybara robot submit the form by clicking on the button.