[rspec-users] requiring "test_notifier/rspec" in spec,opts
dbatshaw at gmail.com
Tue Mar 2 17:56:21 EST 2010
If I add to spec.opts '--require test_notifier/rspec' (quotes are
removed) it is finding it but I am encountering the same error as if I
didn't require the file early enough in spec_helper:
/usr/local/lib/site_ruby/1.8/rubygems.rb:270:in `activate': You have a
nil object when you didn't expect it! (NoMethodError)
You might have expected an instance of Array.
The error occurred while evaluating nil.map
No sure they same problem won't occur when using the option on the
On Mar 2, 1:13 pm, drewB <dbats... at gmail.com> wrote:
> I may not have been clear. When I said if I add it to the top of my
> spec.opts file, I meant adding, '--require "test_notifier/rspec"'.
> Nevertheless, I tried you suggestion (a very good one).
> Unfortunately, it seems that it must be required before "require
> or the following error appears:
> /usr/local/lib/site_ruby/1.8/rubygems.rb:270:in `activate': You have a
> nil object when you didn't expect it! (NoMethodError)
> You might have expected an instance of Array.
> The error occurred while evaluating nil.map
> On Mar 2, 11:33 am, David Chelimsky <dchelim... at gmail.com> wrote:
> > On Tue, Mar 2, 2010 at 1:22 PM, drewB <dbats... at gmail.com> wrote:
> > > There is a nice little gem that gives you desktop notifications of
> > > your spec commands called test_noitifer (http://github.com/fnando/
> > > test_notifier). I can get it to work by including require
> > > "test_notifier/rspec" toward the top of my spec_helper, or by manually
> > > including it in the command line like:
> > > spec <spec file> --require "test_notifier/rspec"
> > > However, if I add it to the top of my spec.opts file, I get the
> > > following error:
> > > /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > > `gem_original_require': no such file to load -- "test_notifier/
> > > rspec" (LoadError)
> > > Any ideas on how to make it work? I don't want to add it to
> > > spec_helper because then others on my team would need to use the gem
> > > as well (which they might not want to).
> > spec.opts is not a ruby file, so you can't put it there. Why not add
> > it to a ruby file in spec/support/ that you don't keep in source
> > control?
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
More information about the rspec-users