# Run/Debug Configuration: Mocha

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/go/2026.3/llms.txt).

Create: `Run | Edit Configurations |` ![Add New Configuration](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg) `| Mocha`

This page describes the configuration-specific items as well as [options](#common) that are common for all run/debug configurations. For more information about using this configuration, refer to  [Mocha](running-unit-tests-on-mocha.html).

In this dialog, create configurations for running and debugging JavaScript unit tests using the Mocha test framework.

## 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+Comma` (VSCode), `⌘ Comma` (VSCode (macOS)) to open settings and then select `Plugins`.  In the search field, type JavaScript and TypeScript. For more information about plugins, refer to [Managing plugins](managing-plugins.html).

3. Install and enable the Node.js plugin on the Settings | Plugins page, as described in [Installing plugins from
JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo).

## Mocha-specific configuration settings

| Item | Description |
| --- | --- |
|  Node runtime  |   In this field,     specify the Node.js runtime to use. Choose one of the configured runtimes or click ![the Browse button](https://resources.jetbrains.com/help/img/idea/2026.3/app.general.ellipsis.svg) and configure a new one. If you choose the `Project`  alias, GoLand will automatically use the project default interpreter from the Node runtime field .     |
|  Node options  |     In this field, type  the Node.js-specific command-line options to be passed to the Node.js executable file.       |
|  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.      |
|  Environment variables  |      In this field, specify the custom [environment         variables](https://www.w3schools.com/nodejs/nodejs_environment.asp) for the Node.js executable file.        The definitions of variables are displayed in the Environment variables field with semicolons (`;`) as separators, for example:        * `NODE_PATH` A list of additional directories to search when resolving modules. To separate directories in a list, use colon (`:`) on macOS or Linux, use semicolon (`;`) on Windows.    * `NODE_MODULE_CONTEXTS` Set to 1 to load modules in their own global contexts.    * `NODE_DISABLE_COLORS` Set to 1 to disable colors in the REPL.     ![Environment variables](https://resources.jetbrains.com/help/img/idea/2026.3/nodeEnvironmentVariables.png)    Alternatively, click Browse ![the Edit environment variables](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.inline.variables.svg) to the right of the field and configure a list of variables in the Environment Variables dialog, that opens:                 * Use ![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg), ![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.remove.svg), ![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.copy.svg) and ![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.paste.svg) buttons to manage the list of custom variables.    * The dialog also shows a list of available system environment variables. Clear the Include system environment variables checkbox if you don't want to use the system environment variables for the current configuration.    * Click OK, when ready.      |
|  Mocha package  |     In this field, specify the Mocha installation home `/npm/node_modules/mocha`. If you installed Mocha regularly through the Node Package Manager, GoLand detects the Mocha installation home itself. Alternatively, type the path to executable file manually, or click Browse ![the Browse button](https://resources.jetbrains.com/help/img/idea/2026.3/app.general.ellipsis.svg) and select the location in the dialog, that opens.   |
|  User interface  |  From this list, choose the [interface](http://mochajs.org/#interfaces) according to which the tests in the test folder are written. GoLand will recognize only tests that comply with the chosen interface. If during test execution GoLand runs against a test of another interface, the test session will be canceled with an error. This means that all the tests in the specified test folder must be written according to the same interface and this interface must be chosen from the list.  |
|  Extra Mocha options  |     In this field, specify additional [Mocha command-line options](https://mochajs.org/#usage). 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/help/img/idea/2026.3/app.actions.execute.svg).   |
|  Tests  |     In this area, specify the tests to be executed. The available options are:        * All in directory: choose this option to run all the tests from the files stored in a folder and specify the path to this folder in the Test directory field. To look for tests in the subfolders under the specified directory, select the Include subdirectories checkbox.    * File patterns: choose this option to look for tests in all the files with the names that match a certain. Specify the mask in the Test file patterns field using [glob patterns](https://github.com/isaacs/node-glob#glob), for example: ```SHELL *.test.js ``` If the files with tests are stored in a separate folder, for example, `test`, specify the path to this folder in the pattern relative to the working directory: ```SHELL ./folder1/folder2/test/*.test.js ```    * 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/help/img/idea/2026.3/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/help/img/idea/2026.3/app.expui.general.add.svg) and ![Remove](https://resources.jetbrains.com/help/img/idea/2026.3/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/help/img/idea/2026.3/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/help/img/idea/2026.3/app.expui.general.add.svg) and ![Remove](https://resources.jetbrains.com/help/img/idea/2026.3/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/help/img/idea/2026.3/app.general.expandComponent.svg) to open the command preview.             ![Node.js with Docker: run/debug configuration, Docker container settings](https://resources.jetbrains.com/help/img/idea/2026.3/ws_node_docker_mocha_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/help/img/idea/2026.3/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.                   |

## 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 GoLand stores run configuration settings in `.idea/workspace.xml`.    |

## Stepping tab

On this tab, specify the [stepping](stepping-through-the-program.html#step-into) options.

Some scripts  are skipped by Step into as you normally might not need to debug them. This list can be fine-tuned on the `Build, Execution, Deployment | Debugger | Stepping` page   of the Settings dialog (`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+Comma` (VSCode), `⌘ Comma` (VSCode (macOS))).

Procedure:

1. Open the run/debug configuration to launch a debugging session with and switch to the Stepping tab.

2. To suppress automatic Smart Step Into, clear the Always do smart step into checkbox.

3. To skip scripts from the `ignoreList` field of the sourcemaps, select the Ignore known third party scripts specified in source maps checkbox.

The older Chrome-specific field name `x_google_ignoreList` is deprecated but may still be recognized when the `ignoreList` field is absent. Learn more from the [source map
specification](https://tc39.es/ecma426/#sec-source-map-format).

4. To suppress stepping into custom scripts, select the Do not step into scripts with a URL matching the patterns below checkbox and expand the default list of such scripts below. Use `*`, `?`, `**` and `!`.

![Stepping tab](https://resources.jetbrains.com/help/img/idea/2026.3/rc_stepping_tab.png)

### Pattern syntax

The following characters are supported in patterns:

* An asterisk `*` matches zero or more characters except a slash `/`. Use this character inside a single path part.

* A question mark `?` matches exactly one character except a slash `/`.

* A double asterisk `**` as a whole segment matches zero or more path segments. Its meaning depends on its position: * As the first part, it matches any leading symbols. * As the last part, it matches any trailing symbols. * In the middle, it matches one or more parts. For example, `a/**/b` matches `a/x/b` and `a/x/y/b`but not `a/b`.

* A trailing double asterisk `**` at the end of the last segment (not on its own a full segment, for example, `foo**`) matches any suffix after that segment. For example, `foo**` matches `foo`, `foobar`, and `foo/bar`.

* A pattern that starts with and exclamation mark `!` negates the given pattern and modifies the patterns added before it in the list. It does not add a new pattern of its own.

Example 1
: In the pattern list `["**/*.ts", "!**/*.test.ts"]`, the first glob matches every `.ts` file. The second pattern modifies the first glob to exclude every `.test.ts` file from match.

Example 2
: A passed URL is split into parts by means of a slash `/`. Accordingly, `**/node_modules/**` is split as follows::
:
:
:
: 1.  Double asterisk `**` matches any path before the `node_modules` segment.
:
: 2.  `node_modules` matches against a `node_modules` in the URL.
:
: 3.  Double asterisk `**` matches anything trailing.
:
:
:
: As a result, the pattern `**/node_modules/**` matches any URL that contains `node_modules`.
:
:
:
: Keep in mind that the URLs of the scripts are matched against the whole pattern. If we remove the second double asterisk `**`, the pattern will match any URL that ends with `node_modules` of which there will likely be zero.

Example 3
: Skip the second double asterisk `**` to match against any pattern that ends with a particular filename.
:
:
:
: * `**/app.js` matches all URLs that end with `app.js`.
:
: * The following pattern list will ignore all scripts in `node_modules` except those named `app.js`. ``` **/node_modules/** !**/app.js ```

## 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/help/img/idea/2026.3/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` (VSCode), `⌃ ⏎` (VSCode (macOS)) | Create a run/debug configuration. |
| ![the Remove button](https://resources.jetbrains.com/help/img/idea/2026.3/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` (VSCode), `Alt+Delete` (VSCode (macOS)) |  Delete the selected run/debug configuration. Note that you cannot delete default configurations.  |
|  ![Copy](https://resources.jetbrains.com/help/img/idea/2026.3/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` (VSCode), `Ctrl+D` (VSCode (macOS))  |  Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.  |
| ![Save configuration](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.save.svg) |  | The button is displayed only when you select a [temporary configuration](null). Click this button to save a temporary configuration as permanent.  |
|  ![Move into new folder / Create new folder](https://resources.jetbrains.com/help/img/idea/2026.3/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/help/img/idea/2026.3/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/help/img/idea/2026.3/app.expui.general.moveUp.svg) and ![Move Down](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.moveDown.svg) buttons.       To remove grouping, select a folder and click ![Remove Configuration](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.remove.svg).     |
|  ![Sort configurations](https://resources.jetbrains.com/help/img/idea/2026.3/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/help/img/idea/2026.3/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` (VSCode), `⌃ ⏎` (VSCode (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 GoLand yet, add its definition.    * 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) .    * Run File Watchers: select this option to have GoLand apply all the currently active [File Watchers](using-file-watchers.html).    * Run Remote External tool: adds a remote SSH external tool.    * 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 npm Script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the [npm run/debug configuration settings](null).    * 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.    * Go Command: select to run a Go command before running your program. For example, you can run `go generate` to generate source code before compilation. In the Edit Go Command Task dialog, you can use auto-completion. Auto-completion supports the following commands `generate`, `vet`, `test -i`. You can use your own commands.    |
| ![the Remove button](https://resources.jetbrains.com/help/img/idea/2026.3/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` (VSCode), `Alt+Delete` (VSCode (macOS)) |  Click this icon to remove the selected task from the list.  |
|  ![Edit](https://resources.jetbrains.com/help/img/idea/2026.3/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` (VSCode), `⏎` (VSCode (macOS))  | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.  |
|     ![Method up](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.moveUp.svg)       ![Method down](https://resources.jetbrains.com/help/img/idea/2026.3/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)), `Alt+Up` (VSCode), `Alt+Up` (VSCode (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)), `Alt+Down` (VSCode), `Alt+Down` (VSCode (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)), `Ctrl+Shift+U` (VSCode), `⌘ ⇧ U` (VSCode (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)), `Ctrl+Shift+Y` (VSCode), `⌘ ⇧ D` (VSCode (macOS)).       |

## See also

### Procedures

[Mocha](running-unit-tests-on-mocha.html)

