* I took the conservative approach here: the sinatra code could be removed but that'd cause a regression. (using Sinatra::Application when `app` is not defined) * I left the sinatra tests for now; they should be removed once we're fully confident with rack session ones.
* Webrat::Session.new now take a session adapter class as it's argument and delegates methods such as #response_body and #response_code to an instance of it. * Some of these methods will go away in the future. However, *a lot* of specs depends on them so I've left them for now. The plan is to strip down the session adapter API to these three methods: * request * response_code * response_body * I had to mark a spec as pending: spec/private/rails/rails_session_spec.rb
…he code into Webrat
application_address is used to know where Selenium should navitate to, but we always are booting app servers on 0.0.0.0 so that's where we should verify they exist
This reverts commit 4daf037. This was causing failures in the Weplay selenium suite, where we we're using partial matches. For example: fill_in "Write a message", ... When the markup was: <label>Write a message to Bryan ...</label>