I'm not sure of the intended use of default_host
, but app_host
does what you need. I've found I first need to call the rails session method host!
in order to set the host string that will be passed to controllers in the request object.
Then you need to set Capybara.app_host
to tell Capybara to call your app via the web server instead of just making the calls in process. If you don't do that then Capybara wigs out when it encounters redirects and drops the host information in the second request.
I'm not sure why this doesn't take care of the Rails request
end of things automatically, but I've found that unless I set the host in both places explicitly, then I get inconsistent results.
def set_host (host)
host! host
Capybara.app_host = "http://" + host
end
before(:each) do
set_host "lvh.me:3000"
end
Then you can just use relative paths to access pages.
Update:
Capybara 2.x and rspec-rails 2.12.0 introduced "Feature" specs for running Capybara acceptance tests. The new FeatureExampleGroup
module in rspec-rails
is different from RequestExampleGroup
and no longer has access to the rack-test host!
method. Now you want to use default_url_options
instead:
def set_host (host)
# host! host
default_url_options[:host] = host
Capybara.app_host = "http://" + host
end
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…