chore: migrate to jest v27

[viceice]

Changes:

Migrates to Jest v27

Context:

closes #10159

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added unit tests, or
• No new tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[HonkingGoose]

@viceice does your commit fixing the memory leak maybe also fix issue #5647?

[viceice]

@viceice I was thinking if we could switch to a lighter weight node environment? Maybe we don't need a full JSDOM environment? We might be able to speed up the tests even more... 😄

If it turns out we still need the full fat JSDOM environment for some tests, we could use docblocks comment to mark the parts of the tests that can run in the node environment. That way we could use the lightweight env where possible, and use the full fat env where needed.

Link to Jest blog post: https://jestjs.io/blog/2021/05/25/jest-27 search for the string Running tests in a JSDOM environment to see what Jest has to say about this.

We already use node env 😏

renovate/jest.config.ts

Line 31 in 9209fad

testEnvironment: 'node',

[HonkingGoose]

We already use node env 😏

That was a quick fix! 🤣

[viceice]

@viceice does your commit fixing the memory leak maybe also fix issue #5647?

Nope, i can see it when not running with --logHeapUsage 😕

[viceice]

I think this is ready

[renovate-release]

🎉 This PR is included in version 25.31.12 🎉

The release is available on:

• GitHub release
• 25.31.12

Your semantic-release bot 📦🚀