Support multiple entries in jestrunner.configPath

[laurisvan]

We are running our project as a monorepo with multiple modules, each having their own Jest configuration. Running tests works awesome, but we always need to change jestrunner.configPath in the root-level, shared .vscode/settings.json.

I wonder if vscode-jest-runner could be made support multiple config paths, so that we would not need to change the configuration whenever running tests from a different package than currently?

[twestendorff]

I support the idea. We currently have a Jest configuration for unit and one for integration tests in a project. However, I can only configure one in the settings. This means that I can only execute either unit or integration tests using the plugin.

As a workaround: We can create another Jest configuration, so we then have a Jest unit, a Jest integration and another one that combines the properties of both, in particular testMatch. This way we can set the combined file for the plugin jestrunner.configPath and run the tests using CodeLens. However, this only works as long as the settings are not mutually exclusive.