Closed bthallion closed 6 years ago
The issue is that Chrome 65 is no longer compatible with the version of chromedriver Intern (via Dig Dug) is downloading. A fix is in progress. For now, you can do the following:
"tunnelOptions": {
"drivers": [
{ "name": "chrome", "version": "2.36" }
]
}
node_modules/@theintern/digdug/selenium-standalone
Hey @bthallion there is an incompatibility between the version of chromedriver that intern uses and version 65 of chrome. It has been updated in master of intern but until then you should be able to specify the chrome driver version in your intern config
"tunnel": "selenium",
"tunnelOptions": {
"hostname": "localhost",
"port": 4444,
"drivers": [
{
"name": "chrome",
"version": "2.36"
}
]
That worked, thanks!
See https://github.com/theintern/digdug/issues/60 for some additional info
We are use v3, because v4 is not backward compatible. Can you bump chromedriver for v3 too, pls?
Note to self: We would need to bump both the Intern 3.x minor version and digdug 1.x minor versions since simply having digdug use newer webdriver versions could break functionality for other users of Intern 3.
This has been fixed in Intern 4.2 and Dig Dug 2.1.x
The newest major version of Chrome 65 is causing the chromedriver to fail with this error:
Expected behavior
Intern should be able to launch chromedriver successfully
Current behavior
It's failing to do so
Steps to reproduce (for bugs)
suite('Functional smoke tests', () => { test('type email', async (t) => { await t.remote.setFindTimeout(5000); await t.remote.get(new URL('/index.html', serverUrl)); const email = await t.remote.findByCssSelector('#login-email'); await email.click(); await email.type('someone@hello.com'); assert.isTrue(true); }); });