You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I update the driver version file to something new (which I had to do, because the published version drags behind the repo currently), the automatic driver download fails and the tests fail because of wrong driver version.
It reads the new conf correctly, but already finds an old driver in the .driver folder. That file and the config have hash mismatches, so the plugin ignores the new file, and uses the old one. The old one will probably not work, because the users browser is newer than the old driver.
Also, NONE of this is documented in the readme file.
Suggestion:
document what webdrivers.xml is
document how to update it
document what to do if update fails (delete the .driver folder)
The vaadin plugin could also maybe delete that directory.
The text was updated successfully, but these errors were encountered:
If I update the driver version file to something new (which I had to do, because the published version drags behind the repo currently), the automatic driver download fails and the tests fail because of wrong driver version.
It reads the new conf correctly, but already finds an old driver in the .driver folder. That file and the config have hash mismatches, so the plugin ignores the new file, and uses the old one. The old one will probably not work, because the users browser is newer than the old driver.
Also, NONE of this is documented in the readme file.
Suggestion:
The vaadin plugin could also maybe delete that directory.
The text was updated successfully, but these errors were encountered: