|
|
|
|
|
by mortice
5684 days ago
|
|
There's an assumption implicit in the announcement (and in a lot of anti-Cukes stuff I've seen) that the primary benefit in writing your feature specifications in pseudo-English is that clients get to read/write the features. That's not the point, at least as far as I'm concerned. The point is to make me, as a developer, think like a user and write the specification of a feature from a user's perspective. So instead of writing 'page.should have_css(...),' I write "Then I should see ...", and specify the details of that somewhere else. Yes, I could just write a method 'def i_should_see,' but I'm a developer, and hence lazy and also comfortable with the detail. That means I'm more than likely not to do that, but then I've got a spec which doesn't express the feature from the user's point of view. I'm prepared to accept that there are developers who are disciplined enough to write specs with Steak which do express things from the user's point of view, but I'm certainly not one of them. |
|