Bye-bye, Jest

[paescuj]

So Long, and Thanks for All the Fish

Scope

What's changed:

• Switch Blackbox Tests from Jest to Vitest
  • Migrate package from CJS to ESM
  • Remove copy of utils in favor of import from @directus/utils (wasn't possible due to ESM)
  • Update dependencies (some needed to be kept back due to pure ESM)
  • TS issues clean-up (some appeared after updating tsconfig.json, others already there)

Potential Risks / Drawbacks

• Lot of file changes, albeit about the same in every file
• Vitest runs slightly faster, increasing pressure during tests 😅
• Vitest runs in greater isolation, requiring a temp file to expose data from sequencer to setup/tests - with Jest data could be passed (more easily) via env
  • Might be possible to use Passing serializable data from globalSetup to tests vitest-dev/vitest#4025 (comment) for this once implemented
• In contrast to Jest, Vitest calls the sequencer only after global setup, which means the test flow setup had to be moved from global setup to the common test

Review Questions

• See above ^^
• Additionally:
  • Opted to use MSSQL setup on host instead of Docker container to overcome performance issues which became noticeble with migration to Vitest
  • Currently a placeholder package is required for custom environment, see Failed to load custom environment from JS file vitest-dev/vitest#4237
  • There are still some leftover type issues from previous setup, but I suggest to tackle this separately
    (see new pnpm typecheck command)

Successful test run: https://github.com/directus/directus/actions/runs/6405405868

[rijkvanzanten]

The refactoring generally LGTM. There's too much to realistically go over everything in full detail, but seeing we didn't alter the tests contents and the test still pass, this should be good to go 👍🏻

[licitdev]

LGTM! Hello Vitest! 👋 @paescuj Thank you for the PR~ 💯

On a side note, there are some TS errors in tests but those could be fixed in a separate PR. 🚀