Skip to content

Chrome Setup

Mark Watson edited this page Aug 5, 2016 · 4 revisions

So long as Chrome is installed and working, generally PizzaScript will find it.

However there are bound to be cases where you either don't want the version that PizzaScript finds by default, or PizzaScript is unable to find Chrome in the first place. Here is the basic procedure that we use to look for Chrome:

  1. Use the location specified under chrome.binary in $PWD/setting.ini
  2. If no location specified in 1. check some default locations (differs per OS)
  3. Check the file exists and is executable by the current user. If it is use this file
  4. Otherwise check the path for chrome (Windows), google-chrome (Linux), or Google Chrome (OSX)
  5. If there was no Chrome on the path or it wasn't executable by the current user print an error

The exact logic lives here: ChromeProcess.findChrome().

No automation 'driver' is required for Chrome, this is built-in to PizzaScript. Generally PizzaScript is backward compatible with previous versions of Chrome. Future versions? Well that's somewhat out of our control, but we do run an auto upgrading instance, that should detect issues pretty promptly!

Clone this wiki locally