In this text box, type the Node.js-specific command line options to be passed to the Node.js executable file. See Node Parameters for details.
In this field, specify the working directory of the application. All references in test scripts will be resolved relative to this folder, unless such references use full paths.
By default, the Working directory field shows the project root folder. To change this predefined setting, specify the path to the desired folder or choose a previously used folder from the list.
In this field, specify the environment variables for the Node.js executable file, if applicable. Click the Browse button to the right of the field and configure a list of variables in the Environment Variables dialog box, that opens:
To define a new variable, click the Add toolbar button and specify the variable name and value.
To discard a variable definition, select it in the list and click the Delete toolbar button .
Click OK, when ready
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:
NODE_PATH: A :-separated list of directories prefixed to the module search path.
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.
In this field, specify the Mocha installation home /npm/node_modules/mocha. If you installed Mocha regularly through the Node Package Manager, RubyMine detects the Mocha installation home itself. Alternatively, type the path to executable file manually, or click the Browse button and select the location in the dialog box, that opens.
From this drop-down list, choose the interface according to which the tests in the test folder are written. RubyMine will recognize only tests that comply with the chosen interface. If during test execution RubyMine 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 drop-down list.
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 files stored in a folder. In the Test directory field, specify the folder with the tests. To have RubyMine look for tests in the subfolders under the specified directory, select the Include subdirectories check box.
File pattern: choose this option to have RubyMine look for tests in all the files with the names that match a certain mask and specify the mask in the Test file pattern 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.
Suite: choose this option to run individual suites from a test file. In the Test file field, specify the file where the required suites are defined. Click the Suite name field and configure a list of suites to run. To add a suite to the list, click and type the name of the required suite. To remove a suite, select it in the list and click
Test: choose this option to run individual tests from a test file. In the Test file field, specify the file where the required tests are defined. Click the Test name field and configure a list of tests to run. To add a test to the list, click and type the name of the required test. To remove a test, select it in the list and click
Click this button to add a new configuration to the list.
Click this button to remove the selected configuration from the list.
Click this button to create a copy of the selected configuration.
Click this button to edit the default configuration templates. The defaults are used for newly created configurations.
Alt+Up or Alt+Down
Use these buttons to move the selected configuration or folder up and down in the list.
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
Click this button to sort configurations in alphabetical order.
In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.
This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml.
This check box is not available when editing the run/debug configuration defaults.
Single instance only
If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, RubyMine checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list.
Click this icon to add a task to the list. Select the task to be added:
Run External tool. Select this option to run an application which is external to RubyMine. In the dialog that opens, select the application or applications that should be run. If the necessary application is not defined in RubyMine yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools.
Run Another Configuration. Select this option to have another run/debug configuration executed. In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
Run File Watchers. Select this option to have RubyMine apply all the currently active file watchers, see File Watchers for details.
Run Grunt task. Select this option to run a Grunt task. In the Grunt task dialog box 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 interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run Gulp task. Select this option to run a Grunt task. In the Gulp task dialog box 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 interpreter, the parameters to pass to it, and the path to the gulp package.
Run npm Script. Select this check box to execute an npm script. In the NPM Script dialog box that opens, specify the package.json file where the required script is defined, select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.
Specify the location of the Node.js interpreter and the parameters to pass to it.
If the Check errors check box is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors check box 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 have the source maps for your CoffeeScript sources generated. In the dialog that opens, specify where your CoffeeScript source files are located. For more information, see CoffeeScript.