[Chrome]
exe=“C:\Program Files\Google\Chrome\Application\chrome.exe”
options=‘–load-extension=“%WPTDIR%\extension” --user-data-dir=“%PROFILE%” --new-window --no-proxy-server --no-first-run --no-default-browser-check --enable-experimental-extension-apis’
installer=http://www.webpagetest.org/installers/browsers/chrome.dat
;For SSL support in chrome, enable the downloading of debug symbols
use symbols=1
I also installed this package: http://www.webpagetest.org/installers/browsers/chrome.dat
[hr]
I am against the wall now. Read most of the older threads in this forum to identify a solution but couldn’t succeed. Could someone give me pointers to get out of this situation…
urlblast.ini is only used for IE. If you don’t want IE testing at all then it can be a bit simpler but Chrome and Firefox both share the same location and it’s implicitly the location in user data with a _wptdriver appended.
I see Chrome launching now. Appending “_wptdriver” did the trick !! Specifying location in the wptdriver and utlblast was something i was experimenting, having read through other posts i deleted them earlier.
But i now i have a new challenge. Chrome launches and then crashes immediately.
I got an error which says: “Could not load extension from C:\webpagetest\extension”.
I later read instructions from this URL: Manifest - Version - Chrome Developers and added “manifest”: 2 in manifest.json under C:\webpagetest\extension\manifest.json.
[hr]
I also replaced the content in manifest.json on the test agent from this URL:
What version of the server software are you using? 2.13 is the current release and should have already had new-enough updates in place that you wouldn’t be seeing the issues that you are: Releases · WPO-Foundation/webpagetest · GitHub