Add unit tests back to pipeline & improve VSCode integration

[Splines]

This fixes #571 and it fixes #507.

Ruby Test Explorer extension works now in VSCode. Also see my comment here.

• VSCode integration via Ruby Test Explorer
• Upgrade docs on how to run tests locally, see here
• CI/CD: Run unit tests in pipeline -> see for example this run.

Note

For the Ruby Test Explorer extension to work, you must have a recent python version installed

Currently, the CI/CD test runs take ~4min 30s (with some things already cached). Without any caches it even takes up to ~7min. This is too long and we should try to reduce the time spent in the initial docker build phase. However, this would probably mean restructuring what is done in the dockerfiles, which should probably be something for another PR.

Future Todos

• Fix failing unit tests. ⚠ Should probably be done before merging this. -> Edit: done in this PR.
• Bring Cypress tests back -> try to avoid executing the same Dockerfile again as many tasks can be shared, e.g. copying a .wasm file from the pdfcomprezzor to the project root etc.

Further notes

• Currently, this PR also incorporates changes from Upgrade Node.js dev dependencies & fix ESLint config #636. This is why we should merge Upgrade Node.js dev dependencies & fix ESLint config #636 beforehand ⚠ Note that you must run yarn install locally to have up-to-date dependencies.
• The logs are currently flooded by the following warnings:

DEPRECATION WARNING: BOLD is deprecated! Use MODES[:bold] instead. (called from request at /usr/local/bundle/bundler/gems/sunspot-41a311e9eff3/sunspot_rails/lib/sunspot/rails/log_subscriber.rb:36

These are due to sunspot/sunspot#1039 and we have to wait for the fix (sunspot/sunspot#1038) to be merged.

• To allow for quicker test runs, we precompile the assets when the Docker image (mampf test) is constructed. Therefore, you will probably have to delete the mampf image of the test environment and rebuild it if yours is outdated. The rebuild step is done automatically the next time you try to run the test without the image present. With this approach, you will see the image build in the Output pane -> Ruby Test Explorer Log. An alternative is to just build the image as usual in the terminal yourself, e.g. docker build mampf inside the ./docker/test folder. For more troubleshooting tips, see the wiki.

Additional for reviewers

• Tests should run through locally
• Tests should run through in CI/CD pipeline

[Splines]

Initial setup of the database cleaner was done here: b901205

Maybe related to fix database cleaner issues:

• Truncation not working with multiple schemas
• DB cleaner not cleaning correctly

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (dev@bac18f8). Click here to learn what that means.

Additional details and impacted files

@@          Coverage Diff           @@
##             dev     #581   +/-   ##
======================================
  Coverage       ?   66.62%           
======================================
  Files          ?      309           
  Lines          ?     9388           
  Branches       ?        0           
======================================
  Hits           ?     6255           
  Misses         ?     3133           
  Partials       ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.