OperaDriver is a vendor-supported WebDriver implementation developed by Opera Software and volunteers that implements WebDriver for Opera.

OperaDriver can drive the browser running various tests on your web pages, just as if a real user was navigating through them. It can emulate actions like clicking links, entering text and submitting forms, and reports results back to you so you know that your website works as intended.

OperaDriver's end-user emulation ensures that your entire stack (HTML, scripts, styling, embedded resources and backend setup) is functioning correctly, and this without tedious manual testing routines.

You will need a Java Runtime Environment 1.5 or newer (Oracle or OpenJDK) to use OperaDriver. It uses the Scope interface (same as for Dragonfly) to communicate directly with Opera from Java. Consequently, it is compatible out-of-the-box with Opera version 11.6 or newer, although it works for older versions with some tweaks.

The OperaDriver server expects you to have Opera or Opera Next installed in the default location for each system:

However, you can override this and specify a custom location to Opera by setting the capability opera.path or environmnetal variable OPERA_PATH. You can read more about configuring WebDriver under Advanced Usage.

To use OperaDriver on Opera < 11.52, make sure you set the capabilities opera.port to -1 and opera.profile to "" (empty string) to disable -debugproxy and -pd command-line arguments which older versions of Opera do not support. For even older versions (11.01 or older) you might need a wrapper script (see below).

To get set up please download either selenium-server-standalone or selenium-server and make sure you have a fairly recent version of Opera installed. All you need to do is create a new WebDriver instance:

WebDriver driver = new OperaDriver();
driver.navigate().to("http://opera.com/");

Since WebDriver provides APIs (called bindings) for several languages, you can do the same in Ruby (using the selenium-webdriver gem) by setting the environmental variable SELENIUM_SERVER_JAR to the full path of the selenium-server-standalone JAR you just downloaded:

export SELENIUM_SERVER_JAR=/path/to/selenium-server-standalone.jar

And then do the following in Ruby:

require 'selenium-webdriver'
driver = Selenium::WebDriver.for :opera
driver.navigate.to('http://opera.com/')

In Python you'd set the same environmental variable and invoke Opera this way:

from selenium import webdriver
driver = webdriver.Opera()
driver.get('http://opera.com/')

Since OperaDriver implements the wire protocol, it is fully compatible with any RemoteWebDriver client. Simply start up your server, create a remote client, and away you go:

WebDriver driver = new RemoteWebDriver("http://localhost:9515", DesiredCapabilities.opera());
driver.navigate().to("http://opera.com/");

You can also use OperaDriver as a standalone dependency in your project. Download the package from the Github project's download section and extract it to a location of your choice. To see some examples look at the examples/ directory. For your own projects include the lib/* directory on your classpath, for example:

javac -classpath "lib/*:." Example.java

In Eclipse this can be done under Project → Properties → Java Build Path and then "Add JARs..." or "Add External JARs..." depending on the layout of your project.

You can also use Maven. The group ID is com.opera and the artifact ID is operadriver.

• API documentation
• Selenium WebDriver documentation

You can use the DesiredCapabilities class to specify settings for OperaDriver. The capabilities we support are:

To use capabilities:

DesiredCapabilities capabilities = DesiredCapabilities.opera();
capabilities.setCapability("opera.profile", new OperaProfile("/path/to/existing/profile"));
capabilities.setCapability("opera.logging.level", Level.CONFIG);
capabilities.setCapability("opera.logging.file", "/var/log/operadriver.log");
capabilities.setCapability("opera.display", 8);

// Now use it
WebDriver driver = new OperaDriver(capabilities);
driver.navigate().to("http://opera.com/");

You can also provide a profile for Opera to use. You can use a new, fresh random profile (default) or specify an existing profile on your system. You can manipulate the profile before Opera is started to i.e. set preferences you wish to use:

OperaProfile profile = new OperaProfile();  // fresh, random profile
profile.preferences().set("User Prefs", "Ignore Unrequested Popups", false);

DesiredCapabilities capabilities = DesiredCapabilities.opera();
capabilities.setCapability("opera.profile", profile);

WebDriver driver = new OperaDriver(capabilities);

To specify such things as a custom location of the Opera binary and the command-line arguments to use, you may use environmental variables also. This is a list of the environmental variables which can be set on any operating system:

To set environment variables:

• Linux and Mac: export OPERA_PATH=..., and add this line to ~/.bashrc (or your shell's configuration file) to use in all future sessions.
• Windows: Please follow this guide: http://support.microsoft.com/kb/310519

This is a list of the official Opera Desktop versions supported by OperaDriver:

Some Opera versions don't support the -autotestmode, -debugproxy or -pd arguments sent by OperaDriver by default. You can bypass this problem by creating a wrapper script like this and pointing the capability opera.binary to its absolute path:

#!/bin/sh
# Wrapper to prevent the -autotestmode argument reaching this version of Opera
# which doesn't support it.
`dirname $0`/opera

• Modifier keys' states are not preserved across multiple .sendKeys() calls in Actions
• Problems with Operas with IME feature enabled (Opera Mobile, Android)
• No support for Opera Mini
• No support for JavaScript alert/popup dialogues
• getScreenshotAs() only returns image data of the current viewport, other parts of the image will be black
• Requires Administrator privileges on Windows Vista and 7 when Opera 11.5x is installed in the default location (Program Files)
• Not possible to move into an image enclosed in a link
• Problems with coordinates on moving mouse back and forth past view port
• Tests for typing multibyte characters will fail on Windows unless you have the correct charset
• EcmaScript dblclick events are not triggered when double clicking an element
• Opera requires full focus when testing on Mac