David just posted about the new --patterns option in the trunk. His examples don't include changing the directory structure, but I would think that it would allow that. If not, that would be a good patch.<br><br><a href="http://blog.davidchelimsky.net/articles/2008/01/20/rspec-new-pattern-option">
http://blog.davidchelimsky.net/articles/2008/01/20/rspec-new-pattern-option</a><br><br>-Corey<br><br><div class="gmail_quote">On Jan 23, 2008 3:12 AM, Will Sargent <<a href="mailto:will.sargent@gmail.com">will.sargent@gmail.com
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'd like to change the rspec directory structure from<br><br>/spec<br>
/model<br> /controllers<br> etc<br><br>to<br><br>/spec<br> /unit<br> /models<br> /controllers<br> /lib<br> /functional<br> /models<br> /controllers<br><br>etc.<br><br>Basically the Jay Fields style of testing -- I want the unit tests to
<br>be run all the time on a continuous integration server, but the<br>integration/functional and system tests to be run only once a night.<br><br>How do I break out the rspec tasks so that they cover this heirarchy?<br>It looks like they'll take a pattern, but I don't want to have to
<br>redefine every rake task just to specify this.<br><br>Also, anyone know how hard this would be to maintain? Or if there's<br>an easier way to organize this?<br><br>Will.<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" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.coreyhaines.com">http://www.coreyhaines.com</a><br>The Internet's Premiere source of information about Corey Haines