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
Browser in configuration file are parsed even if browsers are given on the command line #6618
Comments
Thank you for reporting this to us. I was able to reproduce the issue. |
I just noticed that under certain circumstances, the browsers list in the configuration file is checked (including a bad exception if the browser is not found), but then ignored:
Running testcafe through npx directly, or having it in |
Hello @miherlosev, When I launch my tests with testcafe v 1.18.1 from my gitlab pipeline I have the following error "ERROR Cannot find the browser. "edge" is neither a known browser alias, nor a path to an executable file." The browser name provided by the command is ignored. When I launch the same tests with an older version of testcafe, v 1.14.2, everything works fine @miherlosev, cloud you do the test with an other OS than Windows, please? |
Hi @dboujot, Thank you for pointing this out. I was able to reproduce it on a Mac device. Please stay tuned for further updates. |
Hi @AlexanderMoiseev, Thanks for your feedback |
Any personal estimate may be misleading, so we cannot currently tell it at the moment. Once we get any results, we will post them in this thread. |
… valid browser is specified in CLI(closes DevExpress#6618)
Release v1.19.0-alpha.1 addresses this. |
Applies to TestCafé 1.16.1
What is your Test Scenario?
I have a
.testcaferc.json
file such as:Also, I do have Firefox installed but not Internet Explorer.
What is the Current behaviour?
I call
npx testcafe edge tests/ --skip-js-errors
Now I get:
ERROR Cannot find the browser. "ie" is neither a known browser alias, nor a path to an executable file.
What is the Expected behaviour?
Since the browser
edge
is given on the command line, the browsers from the config file should be ignored.This is a change from previous behaviour. At least for 1.10.1, the config file browsers list was ignored. It took me ages to pinpoint the problem when our CI broke: We had a
.testcaferc.json
checked in for local development, but CI tried to use Browserstack instead; now the build broken just saying that chrome was not available.The text was updated successfully, but these errors were encountered: