Hey David, Basically I didn't try that out. Before I received your response I just re-defined all the actions related to authentication with warden, with a nahive implementation of authentication to make the specs run. Not the best solution, but it works.
Thanks anyway for the help given. Regards. On Tue, Feb 9, 2010 at 1:54 PM, David Chelimsky <dchelim...@gmail.com>wrote: > 2010/2/9 Román González <romanand...@gmail.com>: > > Hey guys, > > I'm having some problems on my controller specs regarding authentication. > > Previously I was using restful_authentication on the project, but after a > > major refactoring we changed the authentication code to > > "Warden":http://github.com/hassox/warden (Rack Middleware > authentication). > > When the controller specs are executed, they fail because there is not a > > variable on the request's env set by the Warden middleware. I've read on > a > > previous message that I probably should use an integration test in order > to > > tests this, I used cucumber and test everything successfully. However all > my > > legacy rspec controller tests (that depended on a current_user) are now > > failing. > > Is there a way to patch the rSpec controller API to include this > middleware > > on each test request? > > Controller specs don't go through rack in rails 2, so not really. > > There are integration specs, which wrap the rails integration test API > so you can do anything you can do in a rails integration test. Just > move the files over to spec/integration, convert the requests from > "get :index" to "get 'path/to/index'"and you should be pretty much > good to go. > > Let us know how that works out. > > Cheers, > David > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
