Splitting tests based on file suffix or best practice

[joaomarcelofm]

Hey all!

I'm looking into split the tests we run with Vitest based on the file suffix, something like:

// Default - will run all "*.test.ts" files
pnpm test // (alias to vitest)

// Integration - will only run ".integration-test.ts
pnpm test:integration

Based on the documentation, I could achieve the second option by changing the vitest.config.ts, but that would also change the default runner. I think I could have a second config file dedicated for integration tests, but is it the ideal solution for this?
Any feedback on this is welcome!

[AriPerkkio]

I would recommend to use workspaces:

import { defineWorkspace } from 'vitest/config';

export default defineWorkspace([
    {
        test: {
            name: 'unit',
            include: ['**/*.unit.test.ts'],
        },
    },
    {
        test: {
            name: 'integration',
            include: ['**/*.integration.test.ts'],
            // More integration test related setup here...
        },
    },
]);

You can also create two separate configuration files and pass it as vitest --config ./path/to/vitest.config.ts.

• How to separate unit and integration test #4675
• https://stackblitz.com/fork/github/vitest-dev/vitest/tree/main/examples/workspace?initialPath=__vitest__/

[joaomarcelofm]

Thanks for the tip @AriPerkkio!

In our case, the tests are within the same monorepo app (it's a Nuxt application, and the integration tests are checking Nuxt's server APIs), so I think the split workspaces won't work. Having different configs isn't ideal, but it is also fine here.

[sheremet-va]

Workspace is just a term, you can name it vitest.projects.ts and it will work the same. It exists mainly for performance, and if you just need two different configs, then it's better to have a single workspace with those configs. This is how Vitest vscode extension also works, for example.