Problems with authentication in Capybara

Question

I am testing a feature on a staging server that requires a basic authentication in order to access the site. I got it running by using the following:

Capybara.app_host = "http://user:password@this.isanexample.com"

At one point in the scenario I access a page that uses https instead of http and requires me to put in user and password again in order to continue. It would be easy if I just used visit again, but I actually want to click on a link...

How can I get past this? I have googled like crazy, but couldn't really find a solution that works.

I found this: http://theadmin.org/articles/test-http-basic-authentication-in-rails/, but I have no idea how to implement it. I am quite new to all of this, so I might miss the obvious.

Can someone point me in the right direction?

Here is my code:

env.rb

require 'capybara/cucumber'

Capybara.app_host = "https://user:password@this.isanexample.com"
Capybara.default_driver = :selenium
Capybara.default_wait_time = 5
Capybara.ignore_hidden_elements = true
Capybara.current_session.driver.browser.manage.window.resize_to(1024, 1000)

checkout_steps.rb (abridged)

Given /^I am on the main page$/ do
  visit('/')
end

When /^I navigate to the page with the available boxes$/ do
    page.find(:xpath, "//a[contains(@href,'how-it-works')]").click
    page.find(:xpath, "//a[contains(@class,'join')]").click
end

When /^I choose a monthly subscription$/ do
    page.find(:xpath, "//span[contains(@class,'title') and .[contains(., 'Unbefristetes Abo')]]").click
    page.find_button("Jetzt Bestellen").click
end

@AndreyBotalov: I tried that but I still get the same login dialog. What was your thought behind that suggestion? — TrashyMcTrash, Feb 28 '13 at 08:31
@AndreyBotalov: OK, my bad, I put it in the wrong env.rb at first. But now I do have the problem that once the test starts, I can see the main page (called via env.rb), but after a second the screen goes blanc and the rest of my test fails. Any idea what that could be? — TrashyMcTrash, Feb 28 '13 at 10:05

score 0 · Accepted Answer · answered Jun 28 '13 at 11:38

0

I solved this by getting rid of the authentication on the website itself. If the tests run from within the company network, the authentication popup won't show up anymore. Turns out this is the better solution in a lot of ways.

answered Jun 28 '13 at 11:38

TrashyMcTrash

1,234
2
15
39

Problems with authentication in Capybara

1 Answers1