-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network logging restricts websockets usage #106
Comments
@shawnlobo96 maybe you can help with this issue? :) |
@dimkin-eu Can you execute the tests without Network Logs? Also, BrowserStack only supports secure Web Sockets so could you please confirm if you are using secure Web Sockets only? |
@anthony-fdes , under secure WebSockets you mean wss://? then yes - they are used Thank you for fast heads-up :) |
Hey @dimkin-eu, You can try adding the below capability:
This has been documented under https://www.browserstack.com/automate/capabilities. This should allow WebSocket connections with network logs enabled. The reason for using this capability is mentioned as:
I hope you find this useful :) |
@shawnlobo96 , nice, will check :) This needs some more things, if one testing locally and in Browserstack, will check this too
|
if AUT is using ws for communication - it fails when running on Browserstack, because fails to connect
update - see the workaround in the end
Environment (please complete the following information):
To reproduce
npm install
and thennpm test
package.json
bsSpec.js
wdio.conf.js
Same happens, if BrowserstackLocal started as background service
./BrowserStackLocal --key somekey
Expected behavior
test runs
Actual behavior
using localtesing ws connect fails
Workaround
As turned out - network logging "turns off" ws communication
The text was updated successfully, but these errors were encountered: