# Run/Debug Configuration: Jest > **TL;DR** > Required plugin: > > > > `JavaScript and TypeScript` -  the plugin is bundled with IntelliJ IDEA and enabled by default. Create: `Run | Edit Configurations |` ![Add New Configuration](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg) `| Jest` In this dialog, create configurations for running [Jest](https://jestjs.io/) tests. For more information about creating Vitest tests for JavaScript and TypeScript code, refer to [Vitest features](https://vitest.dev/guide/features.html) on the Vitest official website. ## Before you start Procedure: 1. Download and install [Node.js](http://nodejs.org/#download). 2. Make sure the JavaScript and TypeScript plugin is enabled in the settings. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Plugins`. Click the Installed tab. In the search field, type JavaScript and TypeScript. For more information about plugins, refer to [Managing plugins](managing-plugins.html). ## Jest-specific configuration settings | Item | Description | | --- | --- | | Configuration file | In this field, specify the `jest.config.js` or `jest.config.ts` file to use: select the relevant file from the list, or click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) and select it in the dialog that opens, or just type the path in the field. If the field is empty, IntelliJ IDEA looks for a `package.json` file with a `jest` key. The search is performed in the file system upwards from the working directory. If no appropriate `package.json` file is found, then a [Jest default configuration](https://facebook.github.io/jest/docs/en/configuration.html#options) is generated on the fly. | | Node runtime | In this field, specify the Node.js runtime to use. If you choose the Project alias, IntelliJ IDEA will automatically use the project default interpreter from the Node runtime field on the [JavaScript Runtime](javascript-runtime.html) page . In most cases, IntelliJ IDEA detects the project default runtime and fills in the field itself. You can also choose another configured local or remote interpreter or click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) and configure a new one. | | Node options | In this field, type the Node.js-specific command-line options to be passed to the Node.js executable file. The acceptable options are: * Use `--require coffeescript/register` to have CoffeeScript files compiled into JavaScript on the fly during run. This mode requires that the `register.js` file, which is a part of the `coffeescript` package, is located inside your project. Therefore, make sure you have the `coffeescript` package installed locally as described in [Install the CoffeeScript compiler](coffeescript.html#ws_coffee_installation). * Use `--inspect` or `--inspect-brk` parameter for [Chrome Debugging Protocol](https://developer.chrome.com/devtools/docs/debugger-protocol) support. * To use [ECMAScript Modules](https://jestjs.io/docs/ecmascript-modules) in your project, add the `—experimental-vm-modules` flag to the Node options field. | | Jest package | In this field, specify the location of the jest, react-scripts, react-script-ts, react-super-scripts, or react-awesome-scripts package. | | Working directory | In this field, specify the working directory of the application. By default, the Working directory field shows the project root folder. To change this predefined setting, specify the path to the desired folder. | | Jest options | In this field, type the [Jest CLI options](https://facebook.github.io/jest/docs/en/cli.html) to be passed to Jest. For example, add a `--watch` flag to turn on the autotest-like runner. As a result, any test in the current run configuration restarts automatically on changing the related source code, without clicking the Rerun button ![Rerun](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.execute.svg). | | Environment variables | In this field, optionally specify the environment variables for executing commands. IntelliJ IDEA will show these variables in completion lists for `process.env`. ![Completion for environment variables from Jest run configuration](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_js-jest_test_rc_env_var_completion.png) | | Tests | In this area, specify the tests to be executed. The available options are: * All tests: choose this option to run all the tests from the `jest.config.js` or `jest.config.ts` configuration file or from the generated [Jest default configuration](https://facebook.github.io/jest/docs/en/configuration.html#options). With the default configuration, tests are recognized by the default value of the [testRegex property](https://facebook.github.io/jest/docs/en/configuration.html#testregex-string). * 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. * Suite: choose this option to run individual suites from a test file and specify the path to this file in the Test file field. Click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.open.svg) in the Suite name field and configure a list of suites to run using the ![Add](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg) and ![Remove](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg) 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 ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.open.svg) in the Test name field and configure a list of tests to run using the ![Add](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg) and ![Remove](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg) buttons. | | Docker container settings | This read-only field shows port and volume bindings. Click ![the Expand button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.expandComponent.svg) to open the command preview. > **Warning:** > This field only appears when a [Docker-based remote interpreter](node-with-docker.html#ws_node_docker_configure_remote_interpreter_preferences_remote_interpreters_dialog) is selected. ![Run/debug configuration: Jest. Docker container settings](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_node_docker_jest_run_configuration_docker_container_settings.png) | | Docker Compose | In this area, specify the commands and options to be passed to Docker Compose. Accept the default settings or click ![the Expand button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.expandComponent.svg) and specify custom ones, for example, custom Docker Compose flags, like `--rm` or `--service-ports`. Learn more from the [Docker official website](https://docs.docker.com/compose/reference/). Check the Command Preview. > **Warning:** > This field only appears when a [remote runtime via Docker > Compose](node-with-docker-compose.html#ws_node_docker_compose_configure_interpreter) is selected. | ## Common settings When you edit a run configuration (but not a run configuration template), you can specify the following options: | Item | Description | | --- | --- | | Name | Specify a name for the run configuration to quickly identify it among others when editing or running. | | Store as project file | Save the file with the run configuration settings to share it with other team members. The default location is `.idea/runConfigurations`. However, if you do not want to share the `.idea` directory, you can save the configuration to any other directory within the project. By default, it is disabled, and IntelliJ IDEA stores run configuration settings in `.idea/workspace.xml`. | ## Toolbar The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates. | Item | Shortcut | Description | | --- | --- | --- | | ![the Add button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg) | `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (NetBeans), `Ctrl+N` (Visual Studio), `⌘ N` (Visual Studio (macOS)), `Alt+Insert` (Eclipse), `⌘ N` (Eclipse (macOS)) | Create a run/debug configuration. | | ![the Remove button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg) | `Alt+Delete` (Windows), `⌘ ⌦` (macOS), `⌘ ⌦` (IntelliJ IDEA Classic (macOS)), `⌘ ⌦` (macOS System Shortcuts), `Alt+Delete` (XWin), `Alt+Delete` (GNOME), `Alt+Delete` (KDE), `Alt+Delete` (Emacs), `Alt+Delete` (Sublime Text), `⌘ ⌦` (Sublime Text (macOS)), `Alt+Delete` (NetBeans), `Ctrl+R, D` (Visual Studio), `⌘ R, D` (Visual Studio (macOS)), `Alt+Delete` (Eclipse), `Alt+Delete` (Eclipse (macOS)) | Delete the selected run/debug configuration. Note that you cannot delete default configurations. | | ![Copy](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.copy.svg) | `Ctrl+D` (Windows), `⌘ D` (macOS), `⌘ D` (IntelliJ IDEA Classic (macOS)), `⌘ D` (macOS System Shortcuts), `Ctrl+D` (XWin), `Ctrl+D` (GNOME), `Ctrl+D` (KDE), `Meta+D` (Emacs), `Ctrl+Shift+D` (Sublime Text), `⌘ ⇧ D` (Sublime Text (macOS)), `Ctrl+D` (NetBeans), `Ctrl+D` (Visual Studio), `⌘ D` (Visual Studio (macOS)), `Ctrl+D` (Eclipse), `Ctrl+D` (Eclipse (macOS)) | Create a copy of the selected run/debug configuration. Note that you create copies of default configurations. | | ![Save configuration](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.save.svg) | | The button is displayed only when you select a [temporary configuration](run-debug-configuration.html). Click this button to save a temporary configuration as permanent. | | ![Move into new folder / Create new folder](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app-client.expui.actions.newFolder.svg) | | Move into new folder / Create new folder. You can group run/debug configurations by [placing them into folders](run-debug-configuration.html#config-folders). To create a folder, select the configurations within a category, click ![Folder](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app-client.expui.nodes.folder.svg), and specify the folder name. If only a category is in focus, an empty folder is created. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or ![Move Up](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.moveUp.svg) and ![Move Down](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.moveDown.svg) buttons. To remove grouping, select a folder and click ![Remove Configuration](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg). | | ![Sort configurations](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app-client.expui.objectBrowser.sortAlphabetically.svg) | | Click this button to sort configurations in the alphabetical order. | ## Before launch In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list. | Item | Shortcut | Description | | --- | --- | --- | | ![the Add button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg) | `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (NetBeans), `Ctrl+N` (Visual Studio), `⌘ N` (Visual Studio (macOS)), `Alt+Insert` (Eclipse), `⌘ N` (Eclipse (macOS)) | Click this icon to add one of the following available tasks: * Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger. * Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, refer to [External tools](configuring-third-party-tools.html) and [External tools settings](settings-tools-external-tools.html). * Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a [compound run/debug configuration](run-debug-multiple.html#compound-configs) . * Build: select to compile the specified module. The [Build Module command](compiling-applications.html#compile_module) will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. * Build Project: select to compile the entire project. The [Build Project command](compiling-applications.html#compile_module) will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. * Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results. * Build Artifacts: select this option to build an [artifact](working-with-artifacts.html) or artifacts. In the dialog that opens, select the artifact or artifacts that should be built. * Run Remote External tool: adds a [remote SSH external tool](settings-tools-remote-ssh-external-tools.html). * Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog that opens, specify the `Gruntfile.js` where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the grunt-cli package. * Run Gulp task: select this option to run a Gulp task. In the Gulp task dialog that opens, specify the `Gulpfile.js` where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the gulp package. * Run Maven Goal: select this option to [run a Maven goal](work-with-maven-goals.html). In the dialog that opens, select the goal to be run. * Run npm Script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the [npm run/debug configuration settings](installing-and-removing-external-software-using-node-package-manager.html). * Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: * If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start. * If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched. * Generate CoffeeScript Source Maps: select this option to generate the source maps for your [CoffeeScript](coffeescript.html) sources. In the dialog that opens, specify where your CoffeeScript source files are located. * Run Rake task: add a [Rake task](null) to be executed prior to running or debugging. To choose a Rake task, click the browse button ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg), and select the desired task from the list of available tasks. Note that [code completion](auto-completing-code.html) is available here. ![Code completion for the Rake tasks](https://resources.jetbrains.com.cn/help/img/idea/2026.2/runConfigRakeTask.png) * Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any). | | ![the Remove button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg) | `Alt+Delete` (Windows), `⌘ ⌦` (macOS), `⌘ ⌦` (IntelliJ IDEA Classic (macOS)), `⌘ ⌦` (macOS System Shortcuts), `Alt+Delete` (XWin), `Alt+Delete` (GNOME), `Alt+Delete` (KDE), `Alt+Delete` (Emacs), `Alt+Delete` (Sublime Text), `⌘ ⌦` (Sublime Text (macOS)), `Alt+Delete` (NetBeans), `Ctrl+R, D` (Visual Studio), `⌘ R, D` (Visual Studio (macOS)), `Alt+Delete` (Eclipse), `Alt+Delete` (Eclipse (macOS)) | Click this icon to remove the selected task from the list. | | ![Edit](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.edit.svg) | `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `Enter` (NetBeans), `Enter` (Visual Studio), `⏎` (Visual Studio (macOS)), `Enter` (Eclipse), `⏎` (Eclipse (macOS)) | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens. | | ![Method up](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.moveUp.svg) ![Method down](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.moveDown.svg) | `Alt+Up` (Windows), `⌃ ⇧ ↑` (macOS), `⌃ ↑` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ ↑` (macOS System Shortcuts), `Alt+Up` (XWin), `Alt+Up` (GNOME), `Alt+Up` (KDE), `Alt+Up` (Emacs), `Alt+Up` (Sublime Text), `Alt+Up` (Sublime Text (macOS)), `Ctrl+Alt+Up` (NetBeans), `Alt+Up` (Visual Studio), `⌃ ⇧ ↑` (Visual Studio (macOS)), `Ctrl+Shift+Up` (Eclipse), `⌃ ⌥ ↑` (Eclipse (macOS)) `Alt+Down` (Windows), `⌃ ⇧ ↓` (macOS), `⌃ ↓` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ ↓` (macOS System Shortcuts), `Alt+Down` (XWin), `Alt+Down` (GNOME), `Alt+Down` (KDE), `Alt+Down` (Emacs), `Alt+Down` (Sublime Text), `Alt+Down` (Sublime Text (macOS)), `Ctrl+Alt+Down` (NetBeans), `Alt+Down` (Visual Studio), `⌃ ⇧ ↓` (Visual Studio (macOS)), `Ctrl+Shift+Down` (Eclipse), `⌃ ⌥ ↓` (Eclipse (macOS)) | Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list. | | Show this page | | Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration. | | Activate tool window | | By default this checkbox is selected and the [Run](run-tool-window.html) or the [Debug](debug-tool-window.html) tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` (Windows), `⌘ 4` (macOS), `⌘ 4` (IntelliJ IDEA Classic (macOS)), `⌘ 4` (macOS System Shortcuts), `Alt+4` (XWin), `Alt+4` (GNOME), `Alt+4` (KDE), `Alt+4` (Emacs), `Alt+4` (Sublime Text), `⌘ 4` (Sublime Text (macOS)), `Alt+4` (NetBeans), `Alt+4` (Visual Studio), `⌘ 4` (Visual Studio (macOS)), `Alt+4` (Eclipse), `⌘ 4` (Eclipse (macOS)) or `Alt+5` (Windows), `⌘ 5` (macOS), `⌘ 5` (IntelliJ IDEA Classic (macOS)), `⌘ 5` (macOS System Shortcuts), `Alt+5` (XWin), `Alt+5` (GNOME), `Alt+5` (KDE), `Alt+5` (Emacs), `Alt+5` (Sublime Text), `⌘ 5` (Sublime Text (macOS)), `Alt+5` (NetBeans), `Alt+5` (Visual Studio), `⌘ 5` (Visual Studio (macOS)), `Alt+5` (Eclipse), `⌘ 5` (Eclipse (macOS)). | ## See also ### Procedures [Jest](running-unit-tests-on-jest.html)