After the Node 16 upgrade our non-React JS tests stopped working during CI. After some research, we were made aware that this may be an issue with Firefox not being captured correctly running in a GitHub/GitHub Actions + Karma + Node 16 environment (see karma-runner/karma-firefox-launcher#245).
When we discovered the issue we attempted to move away from Firefox and use a headless version of Chromium instead. We were able to get this working in CI, but ran into issues locally when installing a new dependency (puppeteer) used to facilitate the use of Chromium with Karma.
Currently, we have a method of running the tests locally that we do manually during development. Ideally, we'd like to get these tests working in CI again.
Potential Options:
- We might be able to get Chromium working using puppeteer-core
- Other options like Chrome/PhantomJS/etc as a headless browser
After the Node 16 upgrade our non-React JS tests stopped working during CI. After some research, we were made aware that this may be an issue with Firefox not being captured correctly running in a GitHub/GitHub Actions + Karma + Node 16 environment (see karma-runner/karma-firefox-launcher#245).
When we discovered the issue we attempted to move away from Firefox and use a headless version of Chromium instead. We were able to get this working in CI, but ran into issues locally when installing a new dependency (puppeteer) used to facilitate the use of Chromium with Karma.
Currently, we have a method of running the tests locally that we do manually during development. Ideally, we'd like to get these tests working in CI again.
Potential Options: