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
export BROWSERSTACK_USERNAME=
export BROWSERSTACK_ACCESS_KEY=
Both from the browserstack settings tab of their app
Run node_modules/.bin/testcafe 'browserstack:edge:Windows 10' test/testcafe/regression-tests.js from root of prodperfect keen tracking repository
See error in console output
Expected: This test passes without complaint, just like all the other browsers. The actions performed by testcafe should be seen performed in the video.
Actual: testcafe times out waiting for an element to appear. On timeout, the above error is thrown.
Other Notes: Windows / Edge is the only browser that has this issue. Actually throwing an [Object object] is likely just an indication that testcafe is not driving the browser correctly and instead seeing timeouts. I suspect Edge would complain about a thrown [Object object] no matter what caused the timeout.
The text was updated successfully, but these errors were encountered:
Browser Video: BrowserStack Recording
BrowserStack Report: Here
Running on Browser Stack’s Edge 18.17763.0 / Windows 10.0.0 browser results in:
Uncaught object "[object Object]" was thrown. Throw Error instead.
BrowserStack’s recording shows the test runner timming out “waiting for element to appear.”
Steps to Reproduce
export BROWSERSTACK_ACCESS_KEY=
Both from the browserstack settings tab of their app
Expected: This test passes without complaint, just like all the other browsers. The actions performed by testcafe should be seen performed in the video.
Actual: testcafe times out waiting for an element to appear. On timeout, the above error is thrown.
Other Notes: Windows / Edge is the only browser that has this issue. Actually throwing an [Object object] is likely just an indication that testcafe is not driving the browser correctly and instead seeing timeouts. I suspect Edge would complain about a thrown [Object object] no matter what caused the timeout.
The text was updated successfully, but these errors were encountered: