Browser in configuration file are parsed even if browsers are given on the command line

Applies to TestCafé 1.16.1

What is your Test Scenario?

I have a .testcaferc.json file such as:

{
    "browsers": ["ie", "firefox"]
}

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.

[dboujot]

Hello @miherlosev, I have the same problem than @piefel. I have a .testcaferc.json such as : { "browsers": [ "chrome", "firefox", "edge" ], "src": "tests/e2e/**/*.ts" }

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?

[github-actions[bot]]

Release v1.19.0-alpha.1 addresses this.