This is a WebDriver client for Go. It supports the WebDriver protocol and has been tested with various versions of Selenium WebDriver, Firefox and Geckodriver, and Chrome and ChromeDriver,

selenium is currently maintained by Eric Garrido (@minusnine).

Run

go get github.com/tebeka/selenium

to fetch the package.

The package requires a working WebDriver installation, which can include recent versions of a web browser being driven by Selenium WebDriver.

The API documentation is at https://godoc.org/github.com/tebeka/selenium. See the example and the unit tests for better usage information.

Any issues are usually because the underlying browser automation framework has a bug or inconsistency. Where possible, we try to cover up these underlying problems in the client, but sometimes workarounds require higher-level intervention.

Please feel free to file an issue if this client doesn't work as expected.

Below are known issues that affect the usage of this API. There are likely others filed on the respective issue trackers.

1. Selenium 2 does not support versions of Firefox newer than 47.0.2.

1. Geckodriver GetAllCookies does not return the expiration date of the cookie.
2. Selenium 3 NewSession does not implement the W3C-specified parameters.
3. The Proxy object is misinterpreted by Geckodriver when passed through by Selenium 3.
4. Maximizing the browser window hangs.
5. Geckodriver does not support the Log API because it hasn't been defined in the spec yet.
6. Firefox via Geckodriver (and also through Selenium) doesn't handle clicking on an element.
7. Firefox via Geckodriver doesn't handle sending control characters without appending a terminating null key.

The Geckodriver team recommends using the newest available Firefox version, as the integration is actively being developed and is constantly improving.

The Geckodriver team are actively iterating on support for the W3C standard and routinely break the existing API. Support for the newest Geckodriver version within this API will likely lag for a time after its release; we expect the lag to only be several days to a small number of weeks.

Using Geckodriver without Selenium usually has the above known issues as well.

1. ChromeDriver has not yet implemented the nascent W3C standard. So far, this only means that GetCookie is not available for Chrome.

1. Enabling Javscript support in HTMLUnit using Selenium WebDriver 3.4 seems broken, with the root cause not yet diagnosed.

Patches are encouraged through GitHub pull requests. Please ensure that a test is added for anything more than a trivial change and that the existing tests pass.

See the issue tracker for features that need implementing.

First, download the ChromeDriver binary, the Firefox binary and the Selenium WebDriver JARs:

$ cd vendor
$ go run init.go
$ cd ..

You only have to do this once initially and later when version numbers in init.go change.

Ensure that the chromium binary is in your path. If the binary is named differently, run the tests with the flags --chrome_binary=<binary name>.

Run the tests:

$ go test 

• There is one top-level test for each of:

  1. Chromium and ChromeDriver.
  2. A new version of Firefox and Selenium 3.
  3. An old version of Firefox and Selenium 2.
  4. HTMLUnit, a Java-based lightweight headless browser implementation.
  5. A new version of Firefox directly against Geckodriver.

  There are subtests that are shared between both top-level tests.

• To run only one of the top-level tests, pass one of:

  • -test.run=TestFirefoxSelenium2
  • -test.run=TestFirefoxSelenium3,
  • -test.run=TestFirefoxGeckoDriver,
  • -test.run=TestHTMLUnit, or
  • -test.run=TestChrome.

  To run a specific subtest, pass -test.run=Test<Browser>/<subtest> as appropriate. This flag supports regular expressions.

• If the Chrome or Firefox binaries, the Selenium JAR, the Geckodriver binary, or the ChromeDriver binary cannot be found, the corresponding tests will be skipped.

• The binaries and JAR under test can be configured by passing flags to go test. See the available flags with go test --arg --help.

• Add the argument -test.v to see detailed output from the test automation framework.

To ensure hermeticity, we also have tests that run under Docker. You will need an installed and running Docker system.

To run the tests under Docker, run:

$ go test --docker

This will create a new Docker container and run the tests in it. (Note: flags supplied to this invocation are not curried through to the go test invocation within the Docker container).

For debugging Docker directly, run the following commands:

$ docker build -t go-selenium testing/
$ docker run --volume=${GOPATH?}:/code --workdir=/code/src/github.com/tebeka/selenium -it go-selenium bash

This project is licensed under the MIT license.