Add a flag to browsertime to enable build check for chromedriver versions
Categories
(Testing :: Raptor, task, P3)
Tracking
(Not tracked)
People
(Reporter: kshampur, Unassigned)
References
Details
(Whiteboard: [fxp])
e.g. we should see if we can add a flag upstream to not do this https://github.com/sitespeedio/browsertime/blob/315dde3c8d1453863e3061fe1943dfc1d7378b43/lib/chrome/webdriver/builder.js#L26 (right now it is the default)
Bug 1890666 could have been caught sooner. It would be convenient to make sure we are always 1:1 matching versions just in case
|
||
Updated•11 months ago
|
|
Reporter | |
Comment 1•10 months ago
|
||
Just realize this is beneficial to keep since android versions are behind desktop, but we do use the latest linux chromedriver for android tests.
so if/when we implement this, we should make sure not to use the flag for mobile tests
|
|
Reporter | |
Comment 2•10 months ago
|
||
(In reply to Kash Shampur [:kshampur] ⌚EST from comment #1)
Just realize this is beneficial to keep since android versions are behind desktop, but we do use the latest linux chromedriver for android tests.
so if/when we implement this, we should make sure not to use the flag for mobile tests
or add an implementation where we start keeping an older chromedriver to 1:1 match android (probably more of a hassle)
|
|
Reporter | |
Comment 3•9 months ago
|
||
(In reply to Kash Shampur [:kshampur] ⌚EST from comment #1)
Just realize this is beneficial to keep since android versions are behind desktop, but we do use the latest linux chromedriver for android tests.
so if/when we implement this, we should make sure not to use the flag for mobile tests
Based on Bug 1900471, I was mistaken - the android CaR should not be behind in version compared to desktop. So having had this flag we could have caught 1900471 a bit earlier
Description
•