[rspec-users] spec'ing the existence of #require

[Chuck Remes]

On Aug 31, 2008, at 12:42 PM, Scott Taylor wrote:

>
> On Aug 31, 2008, at 10:36 AM, Chuck Remes wrote:
>
>> I looked through the mailing list archive but unfortunately my  
>> search terms are too generic (spec and require...).
>>
>> I am writing ruby code that runs under jruby in an embedded  
>> environment. Periodically I will install new code that passes all  
>> specs only to have it fail when it can't find a new class I defined  
>> (missing #require).
>>
>> My spec_helper.rb file does a wildcard search and loads all rb  
>> files in the tree,
>
> Why?  Why don't you just have it load lib/your_project_name.rb,  
> which requires everything else?

I don't know. Is that the right way to do it? The way I am doing it  
now mimics how the rspec gem includes all of the rspec files for  
testing, so I took that as an accepted practice. I'll be happy to try  
your method if it doesn't have a hidden gotcha too.

cr