Run/Debug Configuration: Cucumber

This feature is supported in the Ultimate edition only.

Use this dialog box to define run/debug configuration for Cucumber features.

The dialog box consists of the following tabs:

Configuration tab
Bundler tab
Code Coverage tab
Nailgun tab
Logs tab

Click here for the description of the options that are common for all run/debug configurations.

Configuration tab

Item	Description
Mode	Click one of the radio buttons to define the scope of features: All features in a folder: Click this radio button, if you want to run all features in a directory. Feature file: Click this radio button, if you want to run the specified feature only.
Feature folder	Specify the fully qualified path to the directory that contains the desired features, or click and select the features directory in the dialog that opens. This field is only available, when the All features in folder option is selected.
Feature file	Specify the name of the script to be executed. This field is only available, when the Feature file option is selected.
Element name filter	IntelliJ IDEA will execute the feature elements with the names that contain matching substrings (`-n, --name NAME`).
Tags filter	Specify the tags to be considered on running tests (`-t, --tags TAGS`).
Runner options	Enter runner options. It is important to note that step definitions that reside outside the `Features` directory, can be skipped by IntelliJ IDEA, and the tests will fail to run. Thus, if you want to make use of the step definitions located elsewhere, you have to specify the required directory with the step definition files, or individual step definition files. To to that, add `-r <file or directory name>` to the Runner options field. If the path to a step definition file or directory is relative, it is relative to the Working directory defined in this run/debug configuration.
'cucumber' gem	Use this drop-down list to select the desired gem version, which will be used to run the tests. The list shows the versions that are available in the Ruby SDK. By default, the latest available version is taken.
Use custom Cucumber runner script	Select this check box if you want to use an alternative Cucumber runner script. You can type the fully qualified path to the Cucumber runner script in the text field, or click , and select the desired runner script in the dialog that opens.
Output full backtrace	Select this check box to enable the `--trace` option.
Show the files and features loaded	Select this check box to enable the `-v, --verbose` option.
Use pre-loaded server	From the drop-down list, select the server to be used for executing scripts or examples. Select None if you want to execute a test script or example locally, without any server. If both Zeus and Spork DRb servers are running simultaneously, it is Zeus that gets priority. If a pre-loaded server is already running, it will be selected from the drop-down list. Note that Cucumber features can be run under Zeus server up to version 0.13.4.pre2. Refer to Executing Tests on DRb Server or Executing Tests on Zeus Server for details.
Working directory	Specify the current directory to be used by the running task. By default, the project directory is used as a working directory.
Environment variables	Specify the list of environment variables as the name-value pairs, separated with semi-colons. Alternatively, click the ellipsis button to create variables and specify their values in the Environment Variables dialog box. Formerly, the environment variable `RAILS_ENV` has been implicitly set to `cucumber`, if the user has not explicitly set any other value of this variable. Now this setting is not used any more. If defining the environment variable `RAILS_ENV` is required, the Cucumber default run/debug configuration should be edited.
Ruby arguments	Specify the arguments to be passed to the Ruby interpreter. Classpath property is added to Nailgun settings.
Ruby SDK	Specify the desired Ruby interpreter. You can opt to choose the project default Ruby SDK, or select a different one from the drop-down list of configured Ruby SDKs.

Bundler tab

Item	Description
Run the script in the context of the bundle	If this check box is selected, the script in question will be executed as specified in the `gemfile`.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

Item	Description
Choose code coverage runner	Select the desired code coverage runner. By default, IntelliJ IDEA uses its own coverage engine with the Sampling mode. You can also choose JaCoCo or Emma for calculating coverage.
Sampling	Select this option to measure code coverage with minimal slow-down.
Tracing	Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverage	Select this check box to detect lines covered by one test and all tests covering line. If this check box is selected, becomes available on the toolbar of the coverage statistic pop-up window. This option is only available for the Tracing mode of code coverage measurement for the testing run/debug configurations. Refer to the section Viewing Code Coverage Results.
Merge data with previous results	When you run your unit testing or application configuration several times, use this item to calculate statistics in the Project View, taking into account the statistics of each time you have run the configuration. Finally, the line is considered covered if it is covered at least once.
Packages and classes to record code coverage data	Click and buttons to specify classes and packages to be measured. You can also remove classes and packages from the list by selecting them in the list and clicking the button.
Enable coverage in test folders.	If this check box is selected, the folders marked as test are included in the code coverage analysis.

Nailgun tab

Item Description

Item	Description
Run new instance of the Nailgun server, or use already started one	This check box is only available for JRuby used as the project interpreter. When a run/debug configuration, with this check box selected, is launched, IntelliJ IDEA analyzes the running processes, and does one of the following, depending on the presence of the running Nailgun server: If there is no running Nailgun server, or if there is a Nailgun server on a non-default port, or with a different gemset, then IntelliJ IDEA suggests to specify the desired port number. If a Nailgun server runs on the default port with the required gemset, IntelliJ IDEA does nothing. If a Nailgun server runs on a different port with the required gemset, then IntelliJ IDEA suggests to specify the desired port number. If a Nailgun server runs on the default port with a different gemset, then IntelliJ IDEA deletes the `-ng` argument. If this check box is not selected, then the script is launched in a usual way, without Nailgun.

Run new instance of the Nailgun server, or use already started one

This check box is only available for JRuby used as the project interpreter.

When a run/debug configuration, with this check box selected, is launched, IntelliJ IDEA analyzes the running processes, and does one of the following, depending on the presence of the running Nailgun server:

If there is no running Nailgun server, or if there is a Nailgun server on a non-default port, or with a different gemset, then IntelliJ IDEA suggests to specify the desired port number.
If a Nailgun server runs on the default port with the required gemset, IntelliJ IDEA does nothing.
If a Nailgun server runs on a different port with the required gemset, then IntelliJ IDEA suggests to specify the desired port number.
If a Nailgun server runs on the default port with a different gemset, then IntelliJ IDEA deletes the -ng argument.

If this check box is not selected, then the script is launched in a usual way, without Nailgun.

Logs tab

Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.

Item	Description
Is Active	Select check boxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
Log File Entry	The read-only fields in this column list the log files to show. The list can contain: Full paths to specific files. Ant patterns that define the range of files to be displayed. Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown. If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.
Skip Content	Select this check box to have the previous content of the selected log skipped.
Save console output to file	Select this check box to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.
Show console when a message is printed to standard output stream	Select this check box to activate the output console and bring it forward if an associated process writes to Standard.out.
Show console when a message is printed to standard error stream	Select this check box to activate the output console and bring it forward if an associated process writes to Standard.err.
	Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
	Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
	Click this button to remove the selected log entry from the list.
	Click this button to edit the select log file entry. The button is available only when an entry is selected.

Toolbar

Item	Shortcut	Description
	`Alt+Insert`	Click this button to add a new configuration to the list.
	`Alt+Delete`	Click this button to remove the selected configuration from the list.
	`Ctrl+D`	Click this button to create a copy of the selected configuration.
	Edit defaults	Click this button to edit the default configuration templates. The defaults are used for newly created configurations.
or	`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.
	Move into new folder / Create new folder	Use this button to create a new folder. 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.
	Sort configurations	Click this button to sort configurations in alphabetical order.

Common options

Item Description

Name In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.

Defaults 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.

If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate .xml file in the .idea\runConfigurations folder if the run/debug configuration is shared, or in the .idea\workspace.xml file otherwise.

If the file-based format is used, the settings are stored in the .ipr file for shared configurations, or in the .iws file otherwise.

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, IntelliJ IDEA 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.

Before launch

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.

Item	Keyboard shortcut	Description
	`Alt+Insert`	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 IntelliJ IDEA. In the dialog that opens, select the application or applications that should be run. If the necessary application is not defined in IntelliJ IDEA yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools. Make. Select this option to have the project or module compiled. The Make Module command will be carried out if a particular module is specified in the run/debug configuration, and the Make Project command otherwise. If an error occurs during the compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. Make, no error check. The same as the Make option but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation result. Build Artifacts. Select this option to have an artifact or artifacts built. In the dialog that opens, select the artifact or artifacts that should be built. See also, Working with Artifacts. 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 Ant target. Select this option to have an Ant target run. In the dialog that opens, select the target to be run. For more information, see Ant. 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. Compile TypeScript. Select this option 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 check box to configure the behaviour of the compiler in case any errors are detected: 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 Support. Run Maven Goal. Select this option to have a Maven goal run. In the dialog that opens, select the goal to be run. For more information, see Maven. Run Remote External tool: Add a remote SSH external tool. Refer to the section Remote SSH External Tools for details. Upload files to Remote Host. Select this option to have the application files automatically uploaded to the server according to the default server access configuration. For more information, see Configuring Synchronization with a Web Server and Uploading and Downloading Files.
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
	`Alt+Up`	Click this icon to move the selected task one line up in the list.
	`Alt+Down`	Click this icon to move the selected task one line down in the list.
Show this page		Select this check box to have the run/debug configuration settings shown prior to actually starting the run/debug configuration.
Active tool window		Select this option if you want the Run/Debug tool windows to be activated automatically when you run/debug your application. This option is enabled by default.

Procedures:

Language and Framework-Specific Guidelines:

Last modified: 18 July 2017

IntelliJ IDEA 2017.1 Help