Issue Details (XML | Word | Printable)

Key: SRC-717
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Erik Beans
Reporter: Dmitry Chirkin
Votes: 1
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Selenium Remote Control

Broken support of Google Chrome on Mac (and Linux)

Created: 23/Jul/09 07:41 AM   Updated: 07/Feb/10 08:47 AM   Resolved: 09/Nov/09 06:09 PM
Component/s: Launcher - Google Chrome
Affects Version/s: 1.0.1
Fix Version/s: None

File Attachments: 1. Text File add_launcher_locations_for_mac_os.patch (1 kB) 07/Feb/10 08:47 AM - Rob Lineweaver
2. Text File patch.txt (4 kB) 09/Nov/09 05:48 PM - Erik Beans

Environment: Mac OS X 10.5.7, Java: Apple Inc. 11.3-b02-83 (1.6.0_13 x86_64)


 Description  « Hide

Can't start google chrome on Mac OS X.

Here the traceback that i see in phpUnit result-window:

RuntimeException: Response from Selenium RC server for getNewBrowserSession(*googlechrome, http://translate.josser.tuuube.nixsolutions.com/).
Failed to start new browser session: java.lang.RuntimeException: Google Chrome could not be found in the path!
Please add the directory containing ''chrome.exe'' to your PATH environment
variable, or explicitly specify a path to Google Chrome like this:
*googlechrome/blah/blah/chrome.exe.

And the selenium-server:

15:36:05.000 INFO - Command request: getNewBrowserSession[*googlechrome, http://url-hrer-sorry-can't-share/] on session null
15:36:05.000 INFO - creating new remote session
15:36:05.132 INFO - Got result: Failed to start new browser session: java.lang.RuntimeException: Google Chrome could not be found in the path!
Please add the directory containing ''chrome.exe'' to your PATH environment
variable, or explicitly specify a path to Google Chrome like this:



Sort Order: Ascending order - Click to sort in descending order
Dmitry Chirkin added a comment - 23/Jul/09 07:42 AM

*googlechrome/blah/blah/chrome.exe on session null


Jan Vilhuber added a comment - 09/Oct/09 11:33 AM

Obviously the remote-server is a bit confused as to which OS it's running on. Here's a capture from a run I just did on ubuntu 9.04:

10:19:01.148 INFO - Java: Sun Microsystems Inc. 14.0-b08
10:19:01.148 INFO - OS: Linux 2.6.28-15-generic i386
10:19:01.157 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
10:19:01.267 INFO - Version Jetty/5.1.x
10:19:01.268 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
10:19:01.269 INFO - Started HttpContext[/selenium-server,/selenium-server]
10:19:01.270 INFO - Started HttpContext[/,/]
10:19:01.275 INFO - Started SocketListener on 0.0.0.0:4444
10:19:01.275 INFO - Started org.mortbay.jetty.Server@18eb9e6
10:19:03.761 INFO - Checking Resource aliases
10:19:03.777 INFO - Command request: getNewBrowserSession[*googlechrome, http://192.168.172.1:8888, ] on session null
10:19:03.780 INFO - creating new remote session
10:19:03.888 INFO - Got result: Failed to start new browser session: java.lang.RuntimeException: Google Chrome could not be found in the path!
Please add the directory containing ''chrome.exe'' to your PATH environment
variable, or explicitly specify a path to Google Chrome like this:
*googlechrome/blah/blah/chrome.exe on session null

I created a soft-line to the chromium-browser executable to be chrome.exe, but that didn't work either (the communication to the process seems wrong, as the arguments show up in the google search window that appears to be the default page).

Basicaly, I'd say that googlechrome support for non-windows doesn't exist yet.


Erik Beans added a comment - 09/Nov/09 05:48 PM

Here is a patch that will fix Google Chrome for linux. It includes 3 changes:

  • adding new path elements for chome
  • adding new locator target of google-chrome
  • adding a no-first-run option for google-chrome and taking out the First Run file creation in the profile
  • removing quotation marks when setting the proxy server which caused a linux chrome process not to actually set the proxy server. This could be a chrome bug on how it parses the linux command line options.

Erik


Erik Beans added a comment - 09/Nov/09 06:09 PM

This is fixed in rev 7566


Rob Lineweaver added a comment - 07/Feb/10 08:47 AM

The original patch on this ticket (patch.txt) only fixed GoogleChromeLocator for Linux; the attached patch (add_launcher_locations_for_mac_os.patch) allows Selenium RC to find and launch Google Chrome on Mac OS (assuming it is installed at the default location).

patch is against http://selenium.googlecode.com/svn/selenium-rc/trunk at r8282.