Configuration tab
| Item | Description |
|---|---|
| Main class | In this text box, specify the fully qualified name of the class to be executed (passed to the JRE).
Type the class name manually or click the Browse button
to open the Choose Main Class dialog box, where you can find the desired class
by name or search through the project.
|
| Program arguments | In this text box, type a list of arguments to be passed to the program in the format you would use in the command line.
If necessary, click the
 button
and type the desired arguments in the Program Parameters dialog box.
Use the same rules as for specifying the VM options. |
| Working directory | In this text box, specify the current directory to be used by the running test. This directory is the
starting point for all relative input and output paths. By default, the field contains the directory
where the project file resides. To specify another directory, click the Browse button
select the directory in the dialog that opens.
|
| VM options | In this text box, specify the string to be passed to the VM for launching Cucumber tests.
Usually this string contains the options such as -mx, -verbose, etc.
If necessary, click When specifying the options, follow these rules:
Note The -classpath option specified in this field overrides the classpath of the module. |
| Environment variables | Click the Browse button
to open the Environment Variables dialog box, where you can create variables and specify their values.
|
| Use classpath of module | From this drop-down list, select one of the modules configured in your project. The classpath and JDK of this module will be used to run your application with the current run configuration. |
| Use alternative JRE | Select this check box to enable defining another JRE than the JRE used by the current project / module. |
| Enable capturing form snapshots | Select this check box to enable the GUI Designer to take snapshots of the GUI components, that can be afterwards converted into a form. |
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 |
| 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.
Note 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.
Tip 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. |
 |
Click this button to define the scope of code coverage analysis. In the Add Pattern
dialog box that opens, type the comma-delimited list of Ruby regular expressions, and specify
whether the matching files should be included into or excluded from code coverage analysis.
The patterns defining files to be included into code coverage analysis, are marked with +; the ones to be excluded are marked with -. Each pattern can be enabled or disabled. To do that, select or clear the check box next to a pattern. By default, all newly created patterns are enabled. |
| Click this button to delete the selected pattern from the list. |
 | Click this button to change the selected code coverage pattern. |
| Do not use the optimized C runtime | Select this check box to enable the option --no-rcovrt. Use this option with discretion, since it significantly slows down performance. |
| Enable coverage in test folders. | If this check box is selected, the folders marked as test  are included in the code coverage analysis. |
or 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:
|
| 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 standard out changes | Select this check box to activate output console and bring it forward, if associated process writes to Standard.out. |
| Show console when standard error changes | Select this check box to activate output console and bring it forward, if 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.
Note The button is available only when an entry is selected. |
Toolbar
| Item | Shortcut | Description |
|---|---|---|
|
| InsertInsert | Click this button to add new configuration to the list. |
|
| DeleteDelete | Click this button to remove the selected configuration from the list. |
| Ctrl+DCtrl+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 the newly created configurations. |
 or 
| Alt+UpControl Up or Alt+DownControl Down | Use these buttons to move the selected configuration or group of configurations (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. |
 | Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created. |
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. | |||||||||||||||||||||
| Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. | |||||||||||||||||||||
| Share |
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 and 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 for the ones that are not shared. 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 make sense, when 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 should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.
|