[TS-1197] feat: use nextest

[GuillaumeDecMeetsMore]

Changed

• Use nextest for running the tests
• Add script for launching tests and use it in Just's config
  • Use a temporary container for the tests + use Ryuk to avoid having containers left running in background without any garbage collection

[mm-zacharydavison]

[question] Could we just use testcontainers for this?

[GuillaumeDecMeetsMore]

Ah I forgot to post my comment about this 😓

I wanted to use testcontainers, but the problems is that Rust by default doesn't have a concept of global "beforeAll" and "afterAll"

nextest does have the feature for beforeAll (as an experimental feature), but from what I understand, it's a "one time thing". So, using testcontainers there or a shell script would mean that the containers would start and be killed before running the tests (because the script/app/context is killed before).

(technically, it would work fine for starting the containers. The issue would be on how to garbage collect them)

Note that with NodeJS, I believe it works by keeping a connection opened to the Ryuk container. This is possible because the NodeJS context ("main context") stays alive as long as the tests are running (and the tests are ran inside this context via the use of the vm module). Once the tests are finished, the app "exits", Ryuk detects that the connection is closed and therefore it can kill the containers.

Here, for Rust, from what I understand, each file of test is like a binary executed independently, so we don't have that "main context" (or it's not accessible from what I searched).

So wrapping everything in a shell script seemed the easiest and less complex 😅

Also worth noting that the garbage collection in testcontainers is not finished testcontainers/testcontainers-rs#577

[mm-zacharydavison]

Works for me!

[notion-workspace]

[cal] Improve development experience