You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.
When running phantomjs driver on Windows, PhantomJSDriverService erronously selects
a blank extension instead of .cmd. This leads to an silent error since DriverService.start
fails to print out any exception from the CommandLine process.
Suggested fix:
1. DriverService.start checks for error and prints it out errors from the command line
process (optional)
2. org.openqa.selenium.os.ExecutableFinder.ENDINGS replace "" with ".cmd" on Windows
Workaround:
* Specify desiredCapabilities phantomjs.binary.path when running Selenium
How to reproduce:
* Run selenium with browserName: phantomjs on Windows. When running with debug output,
Selenium will print lines like "16:18:17.787 DEBUG - Polling http://localhost:37991/status"
and then exit
Context: Installed Selenium and PhantomJs using npm (npm install selenium-standalone
phantomjs). Selenium standalone (under NodeJs) adds node_modules/.bin to PATH, PhantomJs
adds node_modules/.bin/phantomjs.cmd AND node_modules/.bin/phantomjs (for Unix).
An example project here: https://github.com/jhannes/wtddjs
At any rate:
* It's bad that failing to create a process fails silently
* It's seems a mistake for Windows to search for executable without extension
* On Windows, .cmd should be a possible extension
Originally reported on Google Code with ID 7514
Reported by
jhannes
on 2014-06-18 14:18:39- _Attachment: [selenium-phantomjs-windows.patch](https://storage.googleapis.com/google-code-attachments/selenium/issue-7514/comment-0/selenium-phantomjs-windows.patch)_
The text was updated successfully, but these errors were encountered: