The Sauce Labs Cookbook

Sauce Headless

Front End Performance Testing


External Resources

More Info

Page tree
Skip to end of metadata
Go to start of metadata

Authentication dialogs present a challenge for automated testing, because Selenium has no way to interact with them. One solution is to bypass authentication by injecting cookies, setting an authenticated state for the application or site you're testing.

You may need to make a change in the source code of the web app itself so that the cookie is acknowledged, but your tests will run without the need for user credentials.

The basic process to test with cookies is:

  1. Launch the browser on your Sauce Labs VM.

  2. Inject cookies using Selenium.

  3. Open the site / web app you want to test.

  4. Run your tests.

You must be on the same domain that the cookie is valid for in order for this to work.

If the homepage of the site you want to test takes a long time to load, you can try accessing a smaller page (like the 404 page) where you can inject the cookie before accessing the homepage.

Code Sample

You can find additional examples for Java, Python, Ruby, and Perl on the official Selenium Commands and Operations page.
# prereq: Sauce username and accesskey set as environment variables

require 'selenium-webdriver'

url = "http://#{ENV['SAUCE_USERNAME']}:#{ENV['SAUCE_ACCESS_KEY']}".strip

browser = Selenium::WebDriver.for(:remote, :url => url,
				:desired_capabilities => { 
					:browserName => 'firefox',
					:version => '40',
					:platform => 'Windows 7'

	:name => 'CookieName',
	:value => 'CookieValue',
	:path => '/',
	:secure => false


puts "Printing out cookies : #{browser.manage.all_cookies}"

# go to URL / app where authentication was needed / prompted.
# i.e.
# browser.get ''
# ...