Right now, when we deploy WDQS, it runs GUI tests (which is in general a good thing) but that requires Chrome headless (which is not good, since having Chrome should not be required. Otherwise you get:
INFO] Running "qunit:all" (qunit) task [INFO] >> There was an error with headless chrome [INFO] Fatal error: Chromium revision is not downloaded. Run "npm install" or "yarn install" [ERROR] npm ERR! Test failed. See above for more details.
We can not just disable GUI module, like we did for build, since GUI still needs to be built and packaged. And running some of the tests is probably good to. But not the ones needing Chrome. So we should find a way to disable qunit only when deploying, or if not possible, disable "npm test" target for deploy-archiva profile.