Why should tests of an Angular application use the --no-sandbox option of Chrome
I'm not sure why the example code disables the sandbox, but for what it's worth, we leave it on in our test suite and everything is fine. We used to specify --no-sandbox just like the examples, but removed it as a workaround to this issue, which was leaving orphaned chrome processes running after the test had completed.
This is one of the reasons if you are using container for testing.
Sandboxing For security reasons, Google Chrome is unable to providesandboxing when it is running in the container-based environment. Touse Chrome in the container-based environment, pass the --no-sandboxflag to the chrome executable