Warden.test_reset! does not always reset and the user is still logged in

Something I found out recently and might be interesting to all

Warden.test_reset! does not always logout the user successfully before the next spec when specs are with Selenium driver – eg. “js: true”. I don’t know why, but this is the observed behavior. I’ve added a call to “logout” before each system spec that is js: true and this seems to make sure that the user is logged out