9
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 16:39, 15 November 2019
, 15 November 2019Added alternate chromedriver sync method
(Create running on google chrome section and add note about the driver.) |
(Added alternate chromedriver sync method) |
||
| Line 52: | Line 52: | ||
. | . | ||
=== Running on Chrome === | ==== Running on Google Chrome ==== | ||
Chrome releases are tied to a specific version of ChromeDriver -- you will need to ensure the two are aligned. | |||
There are two ways of doing this: | |||
1. Download the ChromeDriver that matches the chrome you wish to run from https://chromedriver.chromium.org/ and specify the path: | |||
./mach browsertime https://www.sitespeed.io -b chrome --chrome.chromedriverPath <PATH/TO/VERSIONED/CHROMEDRIVER> | ./mach browsertime https://www.sitespeed.io -b chrome --chrome.chromedriverPath <PATH/TO/VERSIONED/CHROMEDRIVER> | ||
2. Upgrade the ChromeDriver version in <code>tools/browsertime/package-lock.json </code> (see https://www.npmjs.com/package/@sitespeed.io/chromedriver for versions). | |||
Run <code>npm install</code>. | |||
Launch browsertime as follows: | |||
./mach browsertime https://www.sitespeed.io -b chrome | |||
=== More Examples === | === More Examples === | ||