Test: Cannot run local tests without modifying test config

[patrikmolsson]

When running yarn test on local environment (Arch Linux) I ran into the issues described in: puppeteer/puppeteer#290. Although, just adding the flags as described in the referred issue wasn't enough.

I also had to rename the browser:

Semantic-UI-React/karma.conf.babel.js

Line 32 in 4f29636

browsers: ['ChromeHeadless'],

in the test config file to reflect the key in the customLaunchers:

Semantic-UI-React/karma.conf.babel.js

Line 47 in 4f29636

puppeteer: {

I.e. I renamed ChromeHeadless browser to puppeteer and added the flags --no-sandbox and --disable-setuid-sandbox on the customLauncher, since the flags wasn't respected when trying to run the browser. This leads me to believe the flag present today (--stack-trace-limit 50000) isn't respected as well.

Is this something we need to address? We should maybe communicate how to do the work-around to add the --no-sandbox and --disable-setuid-sandbox flags in case more users run into this issue as well.

[layershifter]

@patrikmolsson Thanks 👍 Feel free to open PR that will contain described changes.

[patrikmolsson]

@layershifter Sure, I'll get to it the upcoming week :)