Ok, so I think I tracked down something a little bit more useful...
After going through the trace, I opened up
#{RADIANT_ROOT}/test/test_helper.rb. After commenting a couple of
lines I suspected, I found that commenting line #13 ( require
'test_help' ) allowed my tests to run. (These are the rudimentary
tests that the extension generator creates, so I don't know if all of
the test functionality is there -- just that it's not erroring
anymore).
I tried finding the actual file this was refering to (one of the
regretably harder things to do in Rails...) by looping through my $:
and seeing if the file existed:
irb(main):004:0> $:.map {|path| puts path if
File.exists?(File.join(path, 'test_help'))}
=> [nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil,
nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil,
nil, nil, nil, nil, nil, nil, nil, nil, nil]
irb(main):005:0> load 'test_help'
MissingSourceFile: no such file to load -- test_help
I don't know why this would mess up something with ResponseAssertions,
but I do know that Rails' dependency loading can be a bear, so that's
what I'm chalking it up to.
So what is "test_help" and why do I need it? And how is everyone else
not having the same problem?
Thanks,
Andrew
On 5/24/07, Andrew O'Brien <[EMAIL PROTECTED]> wrote:
> Hi Dan,
>
> Yep -- it's there:
>
> monkeydrome:/usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/vendor/rails/actionpack/lib/action_controller/assertions
> aobrien$ ls -l
> total 136
> -rw-r--r-- 1 root 501 11047 May 22 17:39 deprecated_assertions.rb
> -rw-r--r-- 1 root 501 1051 May 22 17:39 dom_assertions.rb
> -rw-r--r-- 1 root 501 349 May 22 17:39 model_assertions.rb
> -rw-r--r-- 1 root 501 6805 May 22 17:39 response_assertions.rb
> -rw-r--r-- 1 root 501 5229 May 22 17:39 routing_assertions.rb
> -rw-r--r-- 1 root 501 21836 May 22 17:39 selector_assertions.rb
> -rw-r--r-- 1 root 501 5846 May 22 17:39 tag_assertions.rb
>
> The thing is, I got this same error on a different computer (running
> Ubuntu -- the box I'm using now is a Mac), and I can't think of
> anything they have in common that would mess up dependency loading...
> Unless it's just the fact that I touched them :(
>
> On 5/23/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote:
> >
> > > Hi everyone, I started a thread about this a couple of weeks ago and
> > > just now got back to trying to work on it. I still get a NameError
> > > anytime I run rake test:extensions, even on a brand new instance with
> > > no changes to the default radiant or extension code. Now, from what I
> > > recall from the previous thread, whether or not I'm running Radiant in
> > > instance mode or application mode shouldn't matter -- that's true,
> > > right?
> >
> > Works for me (there's bugs with needing to have your dev db fully migrated
> > before your test db will work, but that won't give the
> > errors you're getting).
> >
> > The only explanation I can think of is that your gem install is stuffed in
> > some way.
> >
> > Do you have the file:
> >
> > /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/vendor/rails/actionpack/lib/action_controller/assertions/response_assertions.rb
> >
> > That's what your error message is complaining about.
> >
> > Dan.
> > _______________________________________________
> > Radiant mailing list
> > Post: [email protected]
> > Search: http://radiantcms.org/mailing-list/search/
> > Site: http://lists.radiantcms.org/mailman/listinfo/radiant
> >
>
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
