View on
MetaCPAN
Daniel Gempesaw > Selenium-Remote-Driver-0.27 > Selenium::Chrome

Download:
Selenium-Remote-Driver-0.27.tar.gz

Dependencies

Annotate this POD

Website

View/Report Bugs
Module Version: 0.27   Source   Latest Release: Selenium-Remote-Driver-1.20

NAME ^

Selenium::Chrome - Use ChromeDriver without a Selenium server

VERSION ^

version 0.27

SYNOPSIS ^

    my $driver = Selenium::Chrome->new;

DESCRIPTION ^

This class allows you to use the ChromeDriver without needing the JRE or a selenium server running. When you refrain from passing the remote_server_addr and port arguments, we will search for the chromedriver executable binary in your $PATH. We'll try to start the binary connect to it, shutting it down at the end of the test.

If the chromedriver binary is not found, we'll fall back to the default Selenium::Remote::Driver behavior of assuming defaults of 127.0.0.1:4444 after waiting a few seconds.

If you specify a remote server address, or a port, we'll assume you know what you're doing and take no additional behavior.

If you're curious whether your Selenium::Chrome instance is using a separate ChromeDriver binary, or through the selenium server, you can check the binary_mode attr after instantiation.

ATTRIBUTES ^

binary

Optional: specify the path to your binary. If you don't specify anything, we'll try to find it on our own via "which" in File::Which.

binary_port

Optional: specify the port that we should bind to. If you don't specify anything, we'll default to the driver's default port. Since there's no a priori guarantee that this will be an open port, this is _not_ necessarily the port that we end up using - if the port here is already bound, we'll search above it until we find an open one.

See "port" in Selenium::CanStartBinary for more details, and "port" in Selenium::Remote::Driver after instantiation to see what the actual port turned out to be.

startup_timeout

Optional: specify how long to wait for the binary to start itself and listen on its port. The default duration is arbitrarily 10 seconds. It accepts an integer number of seconds to wait: the following will wait up to 20 seconds:

    Selenium::Chrome->new( startup_timeout => 20 );

See "startup_timeout" in Selenium::CanStartBinary for more information.

SEE ALSO ^

Please see those modules/websites for more information related to this module.

BUGS ^

Please report any bugs or feature requests on the bugtracker website https://github.com/gempesaw/Selenium-Remote-Driver/issues

When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.

AUTHORS ^

Current Maintainers:

Previous maintainers:

Original authors:

COPYRIGHT AND LICENSE ^

Copyright (c) 2010-2011 Aditya Ivaturi, Gordon Child

Copyright (c) 2014-2015 Daniel Gempesaw

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

syntax highlighting: