You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In VSCode, there is an option to run "Configure and start" on directories in the explorer tree. It is very useful for users with a big Nx monorepo, as the tests often cannot be run from the root as they are to big, and the library being tested must be set before "Start Exclusive test run" can work.
We are in the process of migrating from VSCode to Webstorm, and without this option, a Webstorm run configuration must be created to provide the context in which to run an "Exclusive test run". Depending on the monorepo, this can require hundreds of run configurations to be added manually in Webstorm, which makes the list too long to be readable.
We would appreciate if you provided the "Configure and start" option in the contextual menu for the Webstorm plugin, if possible, so we can bypass creating these launch configuration, or even better, make a "Start exclusive test run with local config" option for exclusive test run to use the first parent directory containing a test config file (like jest.config.ts, for instance).
As an exemple, let's say I have an Nx monorepo with "/libs/shared/app1/feature-login" directory which contains a jest.config.ts file, in a monorepo where most libraries contains such a file and the root of the monorepo also has a jest.config.ts file. We would like an exclusive test run option in the contextual menu / actions where launching it on file "/libs/shared/app1/feature-login/src/myservice.spec.ts" to use the tests configs at "/libs/shared/app1/feature-login/jest.config.ts" instead of those at "/jest.config.ts"
The text was updated successfully, but these errors were encountered:
In VSCode, there is an option to run "Configure and start" on directories in the explorer tree. It is very useful for users with a big Nx monorepo, as the tests often cannot be run from the root as they are to big, and the library being tested must be set before "Start Exclusive test run" can work.
We are in the process of migrating from VSCode to Webstorm, and without this option, a Webstorm run configuration must be created to provide the context in which to run an "Exclusive test run". Depending on the monorepo, this can require hundreds of run configurations to be added manually in Webstorm, which makes the list too long to be readable.
We would appreciate if you provided the "Configure and start" option in the contextual menu for the Webstorm plugin, if possible, so we can bypass creating these launch configuration, or even better, make a "Start exclusive test run with local config" option for exclusive test run to use the first parent directory containing a test config file (like jest.config.ts, for instance).
As an exemple, let's say I have an Nx monorepo with "/libs/shared/app1/feature-login" directory which contains a jest.config.ts file, in a monorepo where most libraries contains such a file and the root of the monorepo also has a jest.config.ts file. We would like an exclusive test run option in the contextual menu / actions where launching it on file "/libs/shared/app1/feature-login/src/myservice.spec.ts" to use the tests configs at "/libs/shared/app1/feature-login/jest.config.ts" instead of those at "/jest.config.ts"
The text was updated successfully, but these errors were encountered: