[backend] extend our vitest config for easier dev process

[labo-flg]

Improved our tooling to be able to run dev tests locally quickly.

the globalSetup for vitest has been refactored and can be piloted by 2 env variables, INIT_TEST_PLATFORM and SKIP_CLEANUP_PLATFORM. We make use of these variables in new yarn scripts:

• run yarn test:dev:init to cleanup your test DB, start a platform, run the loader tests that populates the database. This command won't run any other test.
• once initialized this way, run yarn test:dev:resume <name-of-a-test-file.js> to run the specified test file only, the DB won't be cleaned up after run
• ... or run yarn test:watch:resume <name-of-a-test-file.js> to run in watch mode

This makes developing integration tests much quicker and without having to tweak some config files locally.

As for unit tests, I would still advise to use the vitest integration in the IDE. Nothing beats that as it just won't start a platform, useless for unit tests.

The previous commands still exists ;

• yarn test:dev for 1 complete run (cleanup/setup/all tests suites)
• yarn test:watch for a complete execution in watch mode
• yarn test unchanged, used by CI to run once in silent with coverage

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.68%. Comparing base (f0c79df) to head (cdad59d).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5796      +/-   ##
==========================================
- Coverage   66.68%   66.68%   -0.01%     
==========================================
  Files         540      540              
  Lines       64349    64349              
  Branches     5251     5251              
==========================================
- Hits        42912    42909       -3     
- Misses      21437    21440       +3     

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

[aHenryJard]

Thanks for making tests easier :)

[aHenryJard]

Could you move globalSetup to ts or is it too complex ?
And maybe also tests/02-integration/00-inject/loader-test.js file.

If you have time, this comment is not a blocker at all.

[aHenryJard]

This step is not working on my computer, "test:dev:init" is not working on my computer, I have a error at "Should import creation succeed" step,

[labo-flg]

I suppose you do not have more details ?
Are you sure it's not related to a python client version mismatch on your local setup?

[SouadHadjiat]

I just managed to run this step without any issue

[aHenryJard]

ok testing again now

[aHenryJard]

As a side note, it might be a good time to improve the developper documentation as follow up PR https://docs.opencti.io/latest/development/platform/#for-testing