search

DevExpress / testcafe-browser-provider-browserstack

This is the BrowserStack browser provider plugin for TestCafe.
https://testcafe.io
MIT License
86 stars 65 forks source link

OS X tests not connecting #207

Closed liwanma closed 1 year ago

liwanma commented 1 year ago

I have a test suite that targets the latest versions of firefox (windows), edge (windows), and safari (OS X). Until August 21, our tests were running fine on all three browsers. Now, on safari, the tests get stuck at Safari Can't Open the Page. I've tried targeting Safari 16.5 on Ventura but see the same issue (where they previously used to pass). I then tried running firefox on OSX (Sonoma and Ventura), and they also failed (The connection has timed out).

Testing on windows is still working. Everything runs fine locally.

dgurin-squareup commented 1 year ago

I'm seeing the same issue, as of the same date

aleks-pro commented 1 year ago

Hello @liwanma , @dgurin-squareup ,

I tried to reproduce the issue on Mac OS Ventura and Safari 16.5 using testcafe (version 3.3.0),testcafe-browser-provider-browserstack (version 1.15.1), and Node JS (version 20.1.0), but everything works fine for me. Could you please specify versions of testcafe,testcafe-browser-provider-browserstack, and Node JS you are using?

dgurin-squareup commented 1 year ago

@aleks-pro The issue is reproduced with the same version of testcafe@3.3.0, and testcafe-browser-provider-browserstack@1.15.1, and Node v18

liwanma commented 1 year ago

@aleks-pro testcafe@3.3.0 testcafe-browser-provider-browserstack@1.15.1 Node v16

aleks-pro commented 1 year ago

I did not manage to reproduce the issue on NodeJS versions 16.17.0 and 18.4.0 using the following project: https://github.com/DevExpress/testcafe-browser-provider-browserstack/files/12674653/i270.zip. Please try to reproduce the issue with this project (run the npm ci command first than start tests with the npx testcafe "browserstack:safari@16.5:OS X Ventura" command) and share your results.

liwanma commented 1 year ago

@aleks-pro Your example project is working as you described. Strange enough, my tests have also started working again. Maybe it was an issue on the browserstack side?

aleks-pro commented 1 year ago

Hello,

Maybe it was an issue on the browserstack side?

Possibly, but I cannot say for sure. I am happy to hear that this behavior doesn't reproduce anymore. I will close this issue. If you encounter similar behavior in the future, please create a new issue with a reproducible example.