[rspec-users] Best practices to managing RSpec code for very large projects?

Rick DeNatale rick.denatale at gmail.com
Thu Feb 4 09:51:08 EST 2010


On Thu, Feb 4, 2010 at 9:40 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Thu, Feb 4, 2010 at 8:09 AM, J. B. Rainsberger
> <jbrainsberger at gmail.com> wrote:
>> On Thu, Feb 4, 2010 at 00:12, David Mitchell <monch1962 at 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


More information about the rspec-users mailing list