Beta release of OperaChromiumDriver

November 6th, 2014

Driving the browser

Back in the Presto days, we released several versions of OperaPrestoDriver (formerly known as OperaDriver), a WebDriver implementation for running automated tests on Presto-based Opera instances on desktop and Android. After we switched our Opera for desktop and Opera for Android products to run on Chromium/Blink, such a WebDriver implementation was missing — until today, that is!

OperaChromiumDriver is a WebDriver implementation derived from ChromeDriver and adapted by Opera that enables programmatic automation of Chromium-based Opera products for the desktop and Android platforms. This initial beta release of OperaChromiumDriver can be used on Chromium-based versions of Opera starting from version 26 onward.

About WebDriver

For those not familiar with the WebDriver concept, it is a general purpose library for automating testing across web browsers. WebDriver can run 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 reporting results back to you so you know that your website works as intended. That way, you can easily test if your web application is functioning correctly without tedious manual testing routines.

About this release and the work ahead

This is an initial binary-only beta release for several platforms. You can find the binaries under the releases tab on the GitHub OperaChromiumDriver page.

The plan in the weeks ahead is to extract Opera-specific code from our implementation and to generalize those parts of the code that could handle any Chromium-embedding browser. This code is going to be upstreamed to Chromium soon.

Once that is done, the remaining OperaChromiumDriver source code (using ChromeDriver code as a module) will be posted to our OperaChromiumDriver repository.

Give it a spin

So, have a look at the documentation, give it a spin on Opera 26+ (at present, that means Opera Next or Opera Developer), and let us know how it goes.

And if you find bugs, you are most welcome to report them on GitHub.