Run/Debug Configuration: Scala Test
This section provides descriptions of the configuration-specific items, as well as the toolbar and options that are common for all run/debug configurations.
The dialog box consists of the following tabs:
Configuration tab
Item | Description |
---|---|
Test kind | From this drop-down list, select the scope for your tests and fill in the fields depending on your selection. You can choose from the following options:
|
VM parameters | If necessary, specify the string to be passed to the VM. When specifying JVM options, follow these rules:
If there is not enough space, you can click and enter the string in the dialog that opens. |
Environment variables | Click to open the Environment Variables dialog box where you can create variables and specify their values. |
Test options | Use this field to specify the additional test options. If there is not enough space, you can click and enter the string in the dialog that opens. |
Working Directory | Specify the directory that will act as the current directory when running the test. It will act as the root directory for all relative input and output paths. By default, the directory where the project file resides, is used as a working directory. Type directory name, or click and select the desired directory in the dialog that opens. |
Use classpath and SDK of module | From this drop-down list, select the module whose classpath will be used to run the application. |
Print information messages to console | Select this checkbox if you want to print information messages to the Scala console. |
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Item | Description |
---|---|
Choose 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. Refer to the section : view JUnit tests that cover the line at caret. . |
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. |
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 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. |
Common options
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
Item | Description |
---|---|
Name | In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example. from the Run popup (Shift+Alt+F10). |
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 If the file-based format is used, the settings are stored in the |
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 |
---|---|---|
Alt+Insert | Create a run/debug configuration. | |
Alt+Delete | Delete the selected run/debug configuration. Note that you cannot delete default configurations. | |
| Ctrl+D | Create a copy of the selected run/debug configuration. Note that you create copies of default configurations. |
| Edit Templates | View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations. |
/ | Alt+Up/Alt+Down | Move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration. Default templates of run/debug configurations are always sorted alphabetically. |
| Move into new folder / Create new folder | You can group run/debug configurations by placing them into folders. To create a folder, select the configurations within a category, click , and specify 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-and-drop or and buttons. To remove grouping, select a folder and click . |
| Sort configurations | Click this button to sort configurations in the alphabetical order. |
Templates
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
Item | Description |
---|---|
Configurations available in Run Dashboard | In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations. Note that the dashboard will only display the configuration types for which you have created one ore more configurations. |
Confirm rerun with process termination | The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration.
|
Temporary configurations limit | Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. |
Before Launch options
In this area you can specify tasks that must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Click this icon to add one of the following available tasks:
| |
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/Alt+Down | 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 | If this checkbox is selected, which it is by default, the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5. |