On Thu, Feb 4, 2010 at 9:40 AM, David Chelimsky <dchelim...@gmail.com> wrote: > On Thu, Feb 4, 2010 at 8:09 AM, J. B. Rainsberger > <jbrainsber...@gmail.com> wrote: >> On Thu, Feb 4, 2010 at 00:12, David Mitchell <monch1...@gmail.com> wrote: >> >>> What is the 'best practice' way to structure RSpec code and documentation >>> when testing a very large project, where the RSpec code base has to be >>> maintained and extended over a long period? >> >> I don't mean to be glib, but my blink reaction is that there's nothing >> different between maintaining a large suite of RSpec examples and any >> other large code base. > > +1 > > I don't find this glib at all. The question is a difficult one to > answer in a sentence or two, and I think you sum it up pretty well > with this.
Yep! It's just a small battle in the never-ending war against the increase of entropy. It may seem hard, but remember the more you fight it the more you delay the heat death of the universe! <G> -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
