Skip to main content
1 of 3
alecxe
  • 11.4k
  • 11
  • 51
  • 107

Handling unstable remote selenium server connection

We are currently running end-to-end tests on BrowserStack and tackle flakiness of tests on a daily basis. One of the recent problems was that rarely Protractor temporarily loses connection to the BrowserStack remote selenium server throwing errors like:

Failed: ETIMEDOUT connect ETIMEDOUT 203.51.112.2:80

Is there a way to not fail a test in this case and retry a selenium command? Or, if this is not easily achievable, at least retry a specific test?

alecxe
  • 11.4k
  • 11
  • 51
  • 107