Meteor-Community-Packages / Meteor-Community-Packages/meteor-browser-tests
Problems running with recent Chromium
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
It seems recent Chromium (0.75 and up) do not use `chromeOptions` anymore for custom parameters, but `goog:chromeOptions`. So passing things with `TEST_CHROME_ARGS` does not seem to work anymore? BTW, options I am trying to pass are `--no-sandbox --disable-dev-shm-usage` which seems to be useful in CI context. Not sure if they should not simply be set by default?
Contributor guide
Research direction
Start at the TEST_CHROME_ARGS handling and the browser capability setup. Reproduce the issue with recent Chromium using --no-sandbox and --disable-dev-shm-usage, then verify that custom arguments are passed through goog:chromeOptions and work in the CI context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100