Upgrade to Webpack 5

[chadlwilson]

Fixes #10852

Still needs a lot of help/work

• [ ] Generating type files for css may not be working properly in type-declarations-for-css-modules.js and seemed to be removing necessary fields? This was working earlier on some version of webpack/plugins but possibly has broken along the way. May need to double check.

• [ ] Jasmine Karma tests don't work correctly

• [ ] Fix compilation warning

  [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
  BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
      Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
      Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.

• [ ] Needs a new approach to address creating/parsing of manifests for (micro-frontend) asset serving from Java

• [ ] Check general dev experience works fine

• [ ] Get the regression tests passing

• [ ] Other sanity checks

[ZhangJin233]

Hello Chadlwilson @chadlwilson,

I've noticed that there is room for improvement in the Gocd program, and I'm eager to contribute by developing automation test cases for it. I've successfully run Gocd on my Mac environment, but I'm uncertain about the specific test cases that would be most beneficial. Could you please provide some guidance or advice on which test cases would be most valuable for Gocd? Your input would be greatly appreciated.

[chadlwilson]

Hi @ZhangJin233 - perhaps you want to start a separate discussion over at https://github.com/gocd/gocd/discussions ?

I've noticed that there is room for improvement in the Gocd program, and I'm eager to contribute by developing automation test cases for it. I've successfully run Gocd on my Mac environment, but I'm uncertain about the specific test cases that would be most beneficial. Could you please provide some guidance or advice on which test cases would be most valuable for Gocd? Your input would be greatly appreciated.

If you haven't seen already (it's not well documented), GoCD has a large suite of functional tests which drive the UI and APIs over at https://github.com/gocd/ruby-functional-tests which you should take a look at. It also is possible to run these locally, although can take a bit of work.

The main GoCD repository mainly only has unit and module integration tests, but safety relies upon the functional regression tests which are written in Ruby + Gauge + siteprism/capybara.