I was just going to write with the same issue. I know one approach to testing is to wrap the whole test in a transaction that gets rolled back at the end of the test, so I''m wondering if the test harnesses use that approach under the covers. Anyway, I am trying to get the SaltedLogin generator tests to work and am stuck on test_change_password in the bad_email flow - it seems like, when the email fails and an error is raised, the idea is that the update should be rolled back, but stepping through the code, it appears that transaction_open is false, even though the change_password function is wrapped in a User.transaction() block. Not being able to view the state of the database is making this hard to confirm. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---