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
Selenium WebDriver 3.0 introduced a new environment variable named SELENIUM_PROMISE_MANAGER to disable the ControlFlow inside selenium, which is not necessary when we use async/await: SeleniumHQ/selenium#2969
This is according to an old bug which related with selenium webdriver 2.x non-standard promise, submit by me: SeleniumHQ/selenium#2233
So what we need to do is to test Wechaty PuppetWeb with SELENIUM_PROMISE_MANAGER set to 0
I hope this can make some strange bug disappear, for example, sometimes BrowserDrivergetChromeDriver will hang when calling selenium in unit tests in the last serval months, which will cause the unit test fail with no reason.
The text was updated successfully, but these errors were encountered:
Selenium WebDriver 3.0 introduced a new environment variable named
SELENIUM_PROMISE_MANAGER
to disable theControlFlow
inside selenium, which is not necessary when we useasync
/await
: SeleniumHQ/selenium#2969This is according to an old bug which related with selenium webdriver 2.x non-standard promise, submit by me: SeleniumHQ/selenium#2233
And here's another issue related to this: angular/jasminewd#59
So what we need to do is to test Wechaty PuppetWeb with
SELENIUM_PROMISE_MANAGER
set to0
I hope this can make some strange bug disappear, for example, sometimes
BrowserDriver
getChromeDriver
will hang when calling selenium in unit tests in the last serval months, which will cause the unit test fail with no reason.The text was updated successfully, but these errors were encountered: