cucumber hating on our gigantic sessions
so i'm working on retrofitting an older app with some tests, the authentication system is a piece of work with some users coming in from another site entirely.
and it works for the most part. but cucumber fucking hates it. even though we are configured for storing our session data in the db we were getting errors like: CGI::Session::CookieStore::CookieOverflow (CGI::Session::CookieStore::CookieOverflow)
for some reason story runner fails when more than 4k of session data is written by the controller. regardless of the chosen storage method.
http://rubyforge.org/pipermail/rspec-users/2008-October/009167.html
class CGI class Session def close begin @dbman.close @dbprot.clear rescue Exception => e puts e.inspect end end end end
i would love suggestions on how else to tackle this, or at least where to report this as a bug, but I'm not even sure that the diagnosis is right in so far as blaming story runner.
but for the sake of getting on with things I need to keep this thing from barking at me. Everything appears to be working fine, data is coming back from the session. and jesus, is there plenty in there. but we ain't got time to fight that fight just now.
