NAME
Selenium::PhantomJS - Use GhostDriver without a Selenium server
VERSION
version 0.25
SYNOPSIS
my $driver = Selenium::PhantomJS->new;DESCRIPTION
This class allows you to use PhantomJS via Ghostdriver 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 phantomjs 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 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::PhantomJS instance is using a separate PhantomJS binary, or through the selenium server, you can check the binary_mode attr after instantiation.
my $driver = Selenium::PhantomJS->new;
print $driver->binary_mode;N.B. - if you're using Windows and you installed phantomjs via npm install -g phantomjs, there is a very high probability that we will _not_ close down your phantomjs binary correctly after your test. You will be able to tell if we leave around empty command windows that you didn't start yourself. The easiest way to fix this is to download PhantomJS manually from their website and put it in your c<%PATH%>. If this is a blocking issue for you, let us know in Github; thanks!
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.
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
Aditya Ivaturi <ivaturi@gmail.com>
Daniel Gempesaw <gempesaw@gmail.com>
Luke Closs <cpan@5thplane.com>
Mark Stosberg <mark@stosberg.com>
COPYRIGHT AND LICENSE
Copyright (c) 2010-2011 Aditya Ivaturi, Gordon Child
Copyright (c) 2014 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.