[Rails-core] Re: will_paginate to Rails 3: ActionView, routing oddities

On Tue, Nov 10, 2009 at 04:58, Joshua Peek wrote: > > The failing default route tests are a problem with your test fixtures. Now > you must define > "FooController" if you are going route to it. Or you can > use with_controllers! ['foo', ...]. > Thanks. I put this before my routes declaration:

[Rails-core] Re: will_paginate to Rails 3: ActionView, routing oddities

I added a pending test for the one routing issue. The failing default route tests are a problem with your test fixtures. Now you must define "FooController" if you are going route to it. Or you can use with_controllers! ['foo', ...]. I also suggest you use with_routing do |set| instead of editing

[Rails-core] Re: will_paginate to Rails 3: ActionView, routing oddities

I have submitted tickets for some of the above mentioned issues: - ActionView::Base#assigns - SelectorAssertions loading

[Rails-core] Re: will_paginate to Rails 3: ActionView, routing oddities

On Sat, Nov 7, 2009 at 16:08, Eloy Duran wrote: > > You shouldn't need to instantiate a view yourself anymore. The test case > will set this up for you when render is called and assign the test case > instance variables to it. The theory is that you should be able to work with > it as from a cont

[Rails-core] Re: will_paginate to Rails 3: ActionView, routing oddities

Hey Mislav, I recently rewrote large parts of ActionView::TestCase, so there are probably still some rough edges. You shouldn't need to instantiate a view yourself anymore. The test case will set this up for you when render is called and assign the test case instance variables to it. The th