search

DevExpress / testcafe-browser-provider-saucelabs

This is the Sauce Labs browser provider plugin for TestCafe.
https://devexpress.github.io/testcafe/
MIT License
31 stars 41 forks source link

Browser config not found although it exists #52

Closed franciscolosardo closed 1 year ago

franciscolosardo commented 5 years ago

I get the following error :

Error: Unable to find the browser. “saucelabs:Chrome@77.0:Windows 10” is not a browser alias or path to an executable file. at Object.getBrowserInfo (/MYDIR/node_modules/testcafe/lib/browser/provider/pool.js:84:19)

This happens randomly each test it is run. It's more common to get this error on chrome 77 than on chrome 76, but problem persists with both versions.

Also we are having trouble when taking screenshots on failure : Testcafe failing taking screenshot

Farfurix commented 5 years ago

@franciscolosardo

Hello,

I wasn't able to reproduce the issue on my side: Capture

Could you please provide us with your simple project and environment details. We will examine this behavior in greater detail and check for a suitable solution.

vire commented 4 years ago

I have the same issue on CI

ERROR Unable to find the browser. "saucelabs:Firefox@68:Windows 10" is not a browser alias or path to an executable file.
"testcafe-browser-provider-saucelabs": "1.7.0",
"testcafe": "1.6.1",
AlexKamaev commented 4 years ago

@vire I've checked your command and it works on my machine. You referenced the https://github.com/DevExpress/testcafe/pull/3540 pull request. Does that mean that you do not have issues with older TestCafe versions (1.1.0)?

vire commented 4 years ago

@AlexKamaev on my local dev machine it works 9/10 attempts to run tests against saucelabs, but on CI it crashes every first run, I use testcafe@1.6.1

franciscolosardo commented 4 years ago

@AlexKamaev on my local dev machine it works 9/10 attempts to run tests against saucelabs, but on CI it crashes every first run, I use testcafe@1.6.1

I have the same exact issue. When running locally no problems show up, when running CI on a docker it fails

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

github-actions[bot] commented 1 year ago

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.