OperaPrestoDriver is a vendor-supported WebDriver implementation that enables programmatic automation of Presto-based Opera products (i.e. v12 and older).
Java Other
Switch branches/tags
v1.5 v1.4 v1.3 v1.2 v1.1 v1.0 v0.18 v0.17 v0.16.1 v0.16 v0.15 v0.14 v0.13 v0.12 v0.11 v0.10 v0.9 v0.8.1 v0.8 v0.7.3 v0.7.2 v0.7.1 v0.7 v0.6.1 v0.6 v0.5.2 v0.5.1 v0.5 v0.4.3 v0.4.2 v0.4.2.pre7 v0.4.2.pre6 v0.4.2.pre5 v0.4.2.pre4 v0.4.2.pre3 v0.4.2.pre2 v0.4.2.pre1 v0.4.1 v0.3.6 v0.3.5 v0.2.9 v0.2.8 v0.2.7 v0.2.4 spartan_redux_alpha_2 spartan_redux_alpha_1 spartan-release-186 pre-merge-316240-and-idle builds/zimpel_1066 builds/zimpel_1065 builds/zimpel_1064 builds/zimpel_1063 builds/zimpel_1062 builds/zimpel_1061 builds/zimpel_1060 builds/zimpel_1059 builds/zimpel_1058 builds/zimpel_1057 builds/zimpel_1056 builds/zimpel_1055 builds/zimpel_1054 builds/zimpel_1052 builds/zimpel_1051 builds/zimpel_1050 builds/zimpel_1049 builds/zimpel_1048 builds/zimpel_1047 builds/slave-investigation_13 builds/slave-investigation_12 builds/slave-investigation_11 builds/slave-investigation_10 builds/slave-investigation_9 builds/slave-investigation_8 builds/slave-investigation_7 builds/slave-investigation_6 builds/slave-investigation_5 builds/slave-investigation_4 builds/slave-investigation_3 builds/slave-investigation_2 builds/slave-investigation_1 builds/masterdrv-desktopwtr_2 builds/masterdrv-desktopwtr_1 builds/masterdrv-desktopwtr_0 builds/master_37 builds/master_36 builds/master_35 builds/master_34 builds/master_33 builds/elbing_0 builds/desktop-stable-rebased_4 builds/desktop-stable-rebased_3 builds/desktop-stable-rebased_2 builds/desktop-stable-rebased_1 builds/desktop-stable-rebased_0 builds/DSK-364371_27 builds/DSK-364371_26 builds/DSK-364371_25 builds/DSK-364371_24 builds/DSK-364371_23 builds/DSK-364371_22
Nothing to show
Latest commit 1ccceda Nov 4, 2014 @andreasbovens andreasbovens Update README.md
I've changed more instances of OperaDriver to OperaPrestoDriver



OperaPrestoDriver is a vendor-supported WebDriver implementation developed by Opera and volunteers that enable programmatic automation of Presto-based Opera products (i.e. v12 and older). It is a part of the Selenium project.

Note that OperaPrestoDriver is only compatible with Presto-based Opera browsers up until v12.1*. For Blink-based Operas (v15 and onwards), refer to the OperaChromiumDriver project.

WebDriver is a general purpose library for automating web browsers. It 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, enter text and submitting forms, and reporting results back to you so you know that your website works as intended.

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

OperaPrestoDriver is usable out of the box from the official Selenium packages, and can be used no extra setup on any Presto-based version of Opera.


Getting started

To get set up, first download either the selenium-server-standalone or selenium-server package and make sure you have a fairly recent version of Opera installed in a default location. Finally, all you need to do is create a new OperaDriver instance:

WebDriver driver = new OperaDriver();

If you prefer using a package management system, OperaPrestoDriver is also available through Maven; either as a part of the Selenium package, or as a separate package. The group ID for Selenium is org.openqa.selenium.*, and com.opera and artifact ID operadriver for OperaPrestoDriver specifically.

Other languages

Since WebDriver provides bindings for several programming languages, you can follow the same approach as above in both Python (using the selenium package) and in Ruby (using the selenium-webdriver gem).

The Python equivalent of the above example would be:

from selenium import webdriver
driver = webdriver.Opera()

The same in Ruby:

require 'selenium-webdriver'
driver = Selenium::WebDriver.for :opera

To execute the tests, please ensure that the environmental variable SELENIUM_SERVER_JAR contains the path to the selenium-server-standalone JAR you downloaded earlier.

To execute the Python test:

SELENIUM_SERVER_JAR=/path/to/selenium-server-standalone.jar python test.py

And for Ruby:

SELENIUM_SERVER_JAR=/path/to/selenium-server-standalone.jar ruby test.rb

Running the server as a standalone process

OperaPrestoDriver is fully compatible with the RemoteWebDriver client. This allows you to run tests on a remote computer which is typically very useful in a distributed environment. First, ensure that your Selenium server is running, then create a remote client as usual:

WebDriver driver = new RemoteWebDriver("http://localhost:4444", DesiredCapabilities.opera());


To customize Opera and WebDriver in various ways you may request a certain configuration from the Selenium server. Since not all server implementations supports every WebDriver feature, the client and server should use JSON objects with the properties when describing which features are desirable.

In additon to the general WebDriver capabilities available, OperaPrestoDriver has a number of custom capabilities that may be requested. To request a specific driver configuration you

You can use the DesiredCapabilities class to request a specific driver configuration. The Opera-specific capabilities supported are:

Capability Type Default Description
opera.logging.level Level/String/Integer Level.INFO (String/Level/Integer) How verbose the logging should be. Available levels are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value), ALL, OFF.

The argument may consist of either a level name as a string, an integer value, a Level reference, or null. If the value is neither of a known name nor an integer, an IllegalArgumentException will be thrown.
opera.logging.file File/String null Where to send the output of the logging. Default is to not write to file.
opera.product OperaProduct/String Desktop The product to request, for example OperaProduct#DESKTOP or OperaProduct#MOBILE. It will attempt to locate the product binary based on the operating system's default installation paths if opera.binary is not set.
opera.binary String Default location of Opera on system Path to the Opera binary to use. If not specified, OperaPrestoDriver will guess the path to your Opera installation (typically /usr/bin/opera, C:\Program Files\Opera\opera.exe, or similar).
opera.arguments String null Arguments to pass to Opera, separated by spaces. See opera -help for available command-line switches.
opera.emulationProfile EmulationProfile/JSON object null Allows you to specify an emulation profile to use with Opera Mobile.
opera.host String Non-loopback IP if available, loopback otherwise The host Opera should connect to. Since OperaPrestoDriver works in a client-server relationship to Opera (where Opera is the client, driver the server) you can also run remote instances of Opera on other devices; that be a phone, a TV or another computer.
opera.port Integer Random port The port to Opera should connect to. Setting this capability to 0 will probe for a free, random port, setting it to -1 will ensure compatibility mode using port the default port 7001 for Operas version 11.52 or older.
opera.profile OperaProfile/string temporary profile directory of the profile to use, or an OperaProfile instance object representing a profile. if null is given, a random temporary directory is used. if "", an empty string, then the default ~/.autotest profile directory will be used (for backwards compatibility with opera < 11.60).
opera.autostart Boolean true Whether to auto-start the Opera binary. If false, OperaPrestoDriver will wait for a connection from the browser. Go to "opera:debug", enter the correct host/port information, and hit Connect to connect manually.
opera.detach Boolean false Whether to detach the Opera browser when the driver shuts down. This will leave Opera running.
opera.display Integer null The X display to use. If set, Opera will be started on the specified display. (Only works on GNU/Linux.)
opera.idle Boolean false Whether to use Opera's alternative implicit wait implementation. It will use an in-browser heuristic to guess when a page has finished loading, allowing us with great accuracy tell whether there are any planned events in the document. This functionality is useful for very simple test cases, but not designed for real-world testing. It is disabled by default.
opera.runner String OperaLauncherRunner Allows you to specify which runner to use to control the Opera browser binary process.
opera.launcher String null Path to the launcher binary to use. The launcher is an external wrapper around the browser, and is used for controlling the binary and taking external screenshots. If left blank, OperaPrestoDriver will use a launcher supplied with the package.

OperaPrestoDriver also supports some of the common desired capabilities too:

Custom profile

For instance the OperaPrestoDriver can be made to start the browser with specific command-line arguments using the opera.arguments key. This key should define a list of a command-line arguments that should be passed to the browser on startup. For example, to start Opera with a custom profile:

DesiredCapabilities capabilities = DesiredCapabilities.opera();

OperaProfile profile = new OperaProfile("/path/to/profile");  // prepared profile
capabilities.setCapability("opera.profile", profile);

WebDriver driver = new OperaDriver(capabilities);

Opera Mobile Emulator

Or to tell the Opera Mobile Emulator to use the tablet UI and a specific screen resolution:

DesiredCapabilities capabilities = DesiredCapabilities.opera();

capabilities.setCapability("opera.product", OperaProduct.MOBILE);
capabilities.setCapability("opera.arguments", "-tabletui -displaysize 860x600");

WebDriver driver = new OperaDriver(capabilities);

Emulation profile

An emulation profile may be specified when interacting with Opera Mobile to instruct the emulator to use a certain configuration. You may either give it an instance of OperaMobileEmulation which transparently deserializes into a JSON object, or a JSON object directly:

  profileName: "foo",
  width: 800,
  height: 600,
  ppi: 230,
  ime: "tablet",
  userAgent: "Android"

Logging and X display

Similarly, to increase the logging verbosity and, for GNU/Linux, ask Opera to start on a different X display:

DesiredCapabilities capabilities = DesiredCapabilities.opera();

capabilities.setCapability("opera.logging.level", Level.CONFIG);
capabilities.setCapability("opera.logging.file", "/var/log/operadriver.log");
capabilities.setCapability("opera.display", 8);

WebDriver driver = new OperaDriver(capabilities);


It is also possible to configure a proxy for use with Opera. The proxy configuration is set through the capabilities. You can use the Proxy helper in Selenium to manage it:

DesiredCapabilities capabilities = DesiredCapabilities.opera();

Proxy proxy = new Proxy();
capabilities.setCapability("proxy", proxy);

WebDriver driver = new OperaDriver(capabilities);

Environment variables

To specify a custom location of the Opera binary and the command-line arguments to use, you may also use environmental variables. These are the available variables:

Name Description
OPERA_PATH The absolute path to the Opera binary you want to use. If not set OperaPrestoDriver will try to locate an Opera (desktop or mobile) on your system.
OPERA_ARGS A space-delimited list of arguments to pass on to Opera, e.g. -nowindow, -dimensions 1600x1200, &c. See opera -help or operamobile -help to see available arguments.

To set environment variables:

  • GNU/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

Supported Opera versions


This is a list of the official Opera Desktop versions supported by OperaPrestoDriver. Please note that this Java version of OperaPrestoDriver does not support Chromium-based Opera v15+ — for that, refer to the OperaChromiumDriver project.

Version Workaround/tweaks needed
11.52 Set opera.port to -1 and opera.profile to "" (empty string) to disable -debugproxy and -pd command-line arguments
11.01 -autotestmode command-line argument is not supported, use a wrapper script


Please use one of the prepared builds to use OperaPrestoDriver with Opera Mobile.

OperaPrestoDriver does not support the Chromium-based Opera Mobile builds.

Wrapper script

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

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


While OperaPrestoDriver is officially maintained by Opera, it is free software and would only be possible thanks to many volunteer contributors. If you come across a reproducible bug, please open an issue to submit a bug report.

Even better, you can send a pull request! Any changes you make must follow the Google Coding Standards and have test cases attached to them if you introduce a new feature.

Much of OperaPrestoDriver’s code is shared with the other WebDriver implementations, and for working on this code base you should also familiarize yourself with the Selenium code base. There are also a few tips available for working on Selenium.


If you have problems or questions regarding OperaPrestoDriver or Selenium, there are many channels in which you can seek help:

  • IRC: The #selenium channel on the irc.freenode.org network
  • Mailing lists: The webdriver or selenium-users mailing list