Ask for Help

“Has anyone else had their Selenium tests break after upgrading from rails 2.3.8 to 2.3.11?”

One team was using Rack 1.1.0, Mongrel 1.1.5 and Rails 2.3.8. When they upgraded to Rails 2.3.11, their Selenium tests started failing. After some investigation they found this commit which they used to create a monkeypatch for Rack 1.1.0:

# Back-porting this patch: https://github.com/rack/rack/commit/f6f3c60938ea3b08f3292a2480e6753c293584e5
module Rack
  module Utils
    class HeaderHash < Hash
      def [](k)
        super(@names[k]) if @names[k]
        super(@names[k.downcase])
      end
    end
  end
end

Anyone have a better solution?

“Slower test suite with Spork?”

Spork can speed up the start-up time of your test suite, but has anyone seen it slow down the overall test run? One Pivot was seeing a 10% slowdown in overall suite speed.

Interesting Things

• Postgres can write a lot of stuff to your logs. You can quiet it down with the silent-postgres gem and by adding min_messages to database.yml
• RubyMine 3.1 has support for Spork!