Web mutation testing waits on a Stryker vitest runner that supports Vitest 5 #167

What happens

The web half of the mutation report cannot test anything in repositories on Vitest 5 (identity, template-go-vue). With @stryker-mutator/vitest-runner 10.0.0, the latest release:

• In the default run, Stryker records which tests reach each mutant during the dry run. For each mutant it then asks Vitest for the tests related to the sandboxed file, gets none, and runs nothing. Every mutant comes back Survived with testsCompleted: 0.
• With vitest.related: false, the tests run against every mutant, but no coverage is recorded and no mutant is switched on. Every mutant again comes back Survived.

Reproduced on template-go-vue with src/features/notes/domain/noteText.ts, which its tests cover fully: 25 of 25 mutants "survived". The same happened with --inPlace and with --coverageAnalysis off. On template-go-vue#9, src/app/contract.ts made the run stop with "No tests were executed".

Until it is fixed

The mutation report now names Stryker as not finished in either case, instead of listing false survivors. Go mutation is unaffected.

Done when

• A Stryker vitest runner that supports Vitest 5 is released, or the workflow runs Stryker in a way that activates mutants under Vitest 5
• A web pull request in template-go-vue gets a report with killed mutants