Feature Request: Support having multiple test configs

Expected Behavior

I have a project that in test folder I have unit, integration and functional tests. Each test folder has its own configuration and setup files.

It would be great to have possibility to map different configuration for different test folders.

Example:

{
  jest.instances: {
    "test/unit/*": "jest --config=./test/unit/config.js",
    "test/integration/*": "jest --config=./test/integration/config.js",
    "test/functional/*": "jest --config=./test/functional/config.js",
  }
}

So this way, for the test files under test/unit folder, extension will execute the corresponding command.

Actual Behavior

It doesn’t support this at the moment.

[JPeer264]

Following (as @askirmas suggested) works out of the box with jest. I adapted everything according to @yatki’s needs:

const createProject = (type) => ({
  transform: {
    '^.+\\.(t|j)sx?$': 'ts-jest',
  },
  globals: {
    'ts-jest': {
      isolatedModules: true,
    },
  },
  displayName: type,
  preset: 'ts-jest',
  globalSetup: `./__setup__/${type}/jest.global-setup.ts`,
  setupFilesAfterEnv: [`./__setup__/${type}/jest.setup-after-env.ts`],
  testRegex: `(/test/${type}/.*| (\\.| /)(test|spec))\\.[jt]sx?$`,
});

module.exports = {
  projects: [
    createProject('unit'),
    createProject('integration'),
    createProject('functional'),
  ],
};

With that config debug works just as expected on each folder.

[askirmas]

Done with https://jestjs.io/docs/en/configuration#projects-arraystring--projectconfig like 3+ years ago