This field only appears when a remote interpreter via Docker Compose is selected. Learn more from the Docker official website. Accept the default settings or click and specify custom ones, for example, custom Docker Compose flags, like -rm or -service-ports. In this area, specify the commands and options to be passed to Docker Compose. This field only appears when a Docker-based remote interpreter is selected. This read-only field shows port and volume bindings. Click in the Test name field and configure a list of tests to run using the and buttons. Test: choose this option to run individual tests from a test file and specify the path to this file in the Test file field. Click in the Suite name field and configure a list of suites to run using the and buttons. ![]() Suite: choose this option to run individual suites from a test file and specify the path to this file in the Test file field. Test file: choose this option to run only the tests from one file and specify the path to this file in the Test file field. With the default configuration, tests are recognized by the default value of the testRegex property. The available options are:Īll tests: choose this option to run all the tests from the or configuration file or from the generated Jest default configuration. In this area, specify the tests to be executed. IntelliJ IDEA will show these variables in completion lists for process.env. In this field, optionally specify the environment variables for executing commands. As a result, any test in the current run configuration restarts automatically on changing the related source code, without clicking the Rerun button. For example, add a -watch flag to turn on the autotest-like runner. In this field, type the Jest CLI options to be passed to Jest. To change this predefined setting, specify the path to the desired folder. By default, the Working directory field shows the project root folder. In this field, specify the working directory of the application. In this field, specify the location of the jest, react-scripts, react-script-ts, react-super-scripts, or react-awesome-scripts package. If you are using ECMAScript Modules in your project, IntelliJ IDEA detects them and adds the -experimental-vm-modules flag to the Node options field automatically. Otherwise, by default the debug process will use V8 Debugging Protocol. Use -inspect or -inspect-brk parameter when you are using Node.js v7 for Chrome Debugging Protocol support. Therefore make sure you have the coffeescript package installed locally as described in Install the CoffeeScript compiler. This mode requires that the register.js file, which is a part of the coffeescript package, is located inside your project. ![]() Use -require coffeescript/register to have CoffeeScript files compiled into JavaScript on the fly during run. ![]() In this field, type the Node.js-specific command-line options to be passed to the Node.js executable file. You can also choose another configured local or remote interpreter or click and configure a new one. In most cases, IntelliJ IDEA detects the project default interpreter and fills in the field itself. If you choose the Project alias, IntelliJ IDEA will automatically use the project default interpreter from the Node interpreter field on the Node.js page. In this field, specify the Node.js interpreter to use. ![]() If no appropriate package.json file is found, then a Jest default configuration is generated on the fly. The search is performed in the file system upwards from the working directory. If the field is empty, IntelliJ IDEA looks for a package.json file with a jest key. In this field, optionally specify the or file to use: select the relevant file from the list, or click and select it in the dialog that opens, or just type the path in the field.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |