Having custom before statements might reduce readability a bit - I would argue that if you have many "it" statements that share a common setup, they probably deserve a separate context (a different known state). The shared context makes it possible to reduce duplication that might otherwise come from splitting up contexts, and basically does the same thing as custom before statements would do - only it keeps each context a little more atomic - IMO
<br><br><div><span class="gmail_quote">On 5/3/07, <b class="gmail_sendername">David Chelimsky</b> <<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 5/3/07, Scott Taylor <<a href="mailto:mailing_lists@railsnewbie.com">mailing_lists@railsnewbie.com</a>> wrote:<br>><br>> Would it be desirable to have before and after take a spec name as<br>> well as :each and :all?
<br><br>What do YOU think?<br><br>><br>> Scott<br>> _______________________________________________<br>> rspec-users mailing list<br>> <a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a>
<br>> <a href="http://rubyforge.org/mailman/listinfo/rspec-users">http://rubyforge.org/mailman/listinfo/rspec-users</a><br>><br>_______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">
rspec-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users">http://rubyforge.org/mailman/listinfo/rspec-users</a><br></blockquote></div><br>