…case is when you want to test through a web server sitting in front of your application server.
… into webrat/integrations
I don't think silence_stream.rb should be stored under core_extensions, because the way it's implemented, it simply is no core extension. Also, a grep through webrat source shows that silence_stream is only used inside the selenium support. This is why I added webrat/selenium/silence_stream.rb and require it *before* all other selenium related files in webrat/selenium.rb. It's necessary to include it this early, because if mode is set to :selenium, webrat/selenium.rb is required, which in turn requires webrat/selenium/selenium_session.rb and silence_stream must be available before selenium_session gets required because selenium_session already wants to silence the stream.
I added the implementation to webrat/core/configuration.rb because it seems to me that this always gets read first. I decided to put it inside a util module Webrat::SilentStream and include this where appropriate, instead of altering Kernel.
…s before timing out from an option hash Signed-off-by: Balint Erdi <firstname.lastname@example.org>
…ls if config.ru exists
… completed the ability to configure to work with selenium grid." "
…e is used for ...
…cluded it in SeleniumSession as well as the standard webrat session. Also added save_and_open_screengrab method to SeleniumSession.
… without blowing up.