OK, thanks for that advice. It's not the problem the test is railing on the first assertion. It's the update of the user record that's failing for some reason.
Adam On Dec 6, 1:08 pm, Frederick Cheung <[EMAIL PROTECTED]> wrote: > On Dec 6, 12:59 pm, Adam <[EMAIL PROTECTED]> wrote:> OK, thanks Fred. I guess > it's nothing obvious which is sort of > > reassuring. > > Well there is one thing that I refrained from commenting upon because > I've no idea how you do your authentication, but in my apps > > @request.session[:user] = users(:admin) > > would be > > @request.session[:user] = users(:admin).id > > But that should be quite obvious if you look at test.log (it would say > that processing was halted because the authorization filter redirected > or rendered) > > Fred > > > Adam > > > On Dec 5, 3:27 pm, Frederick Cheung <[EMAIL PROTECTED]> > > wrote: > > > > On 5 Dec 2008, at 14:02, Adam wrote: > > > > > The view works but the test fails. > > > > You need to work out why. stick a breakpoint in the action (or in > > > whatever before filters may be relevant) and see what happens > > > > Fred > > > > > Thanks in advance, > > > > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
