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

J. B. Rainsberger jbrainsberger at gmail.com
Thu Feb 4 16:09:17 EST 2010


On Thu, Feb 4, 2010 at 09:40, 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.

Thanks for that.
-- 
J. B. (Joe) Rainsberger :: http://www.jbrains.ca ::
http://blog.thecodewhisperer.com
Diaspar Software Services :: http://www.diasparsoftware.com
Author, JUnit Recipes
2005 Gordon Pask Award for contribution to Agile practice :: Agile
2010: Learn. Practice. Explore.


More information about the rspec-users mailing list