Chrome Setup

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

However you may not want the version that PizzaScript finds by default. Here is the basic procedure that PizzaScript uses to find Chrome:

1. Use the location specified under chrome.binary in $PWD/setting.ini
2. If no location is specified in step 1. check some default locations (these differ per OS). For each location, check the Chrome binary file exists and is executable by the current user.
3. Otherwise check the path for chrome (Windows), google-chrome (Linux), or Google Chrome (OSX)
4. If Chrome wasn't on the path or the binary wasn't executable by the current user quit with an error

The exact logic lives here: ChromeFinder.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 the travis-ci integration tests against the latest chrome.