I've been reading through the Rspec book to see if I missed any
tricks, and the discussion of before block use for context setup in
sec 12.6 struck me as interesting and something I had a knee-jerk
reaction to.
I think that when you are using nested examples to describe a context
change it is bad
On Sun, Sep 20, 2009 at 9:38 AM, nruth wrote:
> I've been reading through the Rspec book to see if I missed any
> tricks, and the discussion of before block use for context setup in
> sec 12.6 struck me as interesting and something I had a knee-jerk
> reaction to.
>
> I think that when you are usi
David
Thanks for the reply.
I think I wasn't clear with my original post: before blocks work fine,
this is just a readability/comprehension/maintenance concern.
We're using a describe (or context) block to name (or document) a
state, then using a separate before block to set up that state
(contex
My last reply seems to have been swallowed by the Ajax monster.
In brief, my suggestion is just for readability/maintenance. I feel
the describe/context and before blocks are the same thing put in two
places, one being documentation and the other implementation.
Splitting them up like this seems l
Hi all,
I am an university student and these days i am on training period. So i
want to know about ruby on on rails "cucumber and Rspec". If somebody
know about these fields please help me. If not please send me an
tutorials for basic functionality of the cucumber and Rspec.
Thank you.
regards,
Mit