You can view the current implementation status of the WebDriver standard here. ![]() What is our update strategy for this dependency? Is it pinned because of particular Chrome version on our CI infra? Or is there a different reason? If not let’s remove the pin and install latest stable version which will most likely match for the most people and pin it manually on CI. ChromeDriver is available for Chrome on Android and Chrome on Desktop (Mac, Linux, Windows and ChromeOS). ![]() Is there a way to override values in package.json? Can we implement such thing so people can freely override it just like we do this for Ruby bundler?.Now with help of we’ve found that updating chromedriver to the version that matches my Google Chrome (which is currently the stable - 77) does help, however this leaves a lock file in changed state in git: diff -git a/package.json b/package.json ![]() All discovery integration tests are falling for me with Selenium::WebDriver::Error::SessionNotCreatedError: session not created: Chrome version must be between 71 and 75 (Driver info: chromedriver=88 (4a34a70827ac54148e092aafb70504c4ea7ae926),platform=Linux 5.2.86_64 x86_64)
0 Comments
Leave a Reply. |