Projects vs. Coverage

[ElSuture]

Hi Vitest-Team,

I'm struggling a little with Projects and Coverage.

Simplified we have a monorepo with three Projects:

• apps/frontend/
• apps/backend/
• libs/shared/

And a Jenkins-Pipeline with the same three steps in this sequence:

1. libs/shared
2. apps/frontend
3. apps/backend/

Up to now the coverage was determined separately (also in separated folders) in the steps itself.

But now I have read in your documentation that with the new defineProject I cannot define the coverage separately for the projects, only globally, like this:

export default mergeConfig(
  viteBaseConfig,
  defineConfig({
    test: {
      projects: [
        'apps/frontend/vitest.config.ts',
        'apps/backend/vitest.config.ts',
        'libs/shared/utils/vitest.config.ts',
      ],
      coverage: {
        include: ['**/src/**/*.ts'],
        all: true,
        provider: 'v8', // 'istanbul' unfortunately doesn't work
        reporter: ['clover', 'json', 'lcov', ['text', { skipFull: true }]],
        reportsDirectory: 'coverage',
      },
    },
  }),
);

I don't see straight a way to get the coverage only for one project. But in our case, it is meaningful to run the tests one after the other.

Would you recommend running the steps than without coverage and adding an extra step only for all global coverage? Or am I just overlooking something?

Best regards,
ElSuture

[sheremet-va]

You can run projects with --project=name CLI flag if you need to run them separately. One thing you can also do is utilize --merge-reports command. It would looks something like this:

vitest run --project=frontend --reporter=blob --outputFile=reports/frontent.json
vitest run --project=backend --reporter=blob --outputFile=reports/backend.json
vitest run --project=utils --reporter=blob --outputFile=reports/utils.json

vitest run --merge-reports=./reports