Run/Debug Configuration: Test::Unit/Shoulda/MiniTest
Use this dialog box to define run/debug configuration for a Test::Unit, Shoulda, or Minitest test.
The dialog box consists of the following tabs:
Click here for the description of the options that are common for all run/debug configurations.
|Name||In this text box, specify the name of the current run/debug configuration.|
|Mode||Click one of the radio buttons to define the scope of tests to be performed:
|Test folder||Type in the text field the fully qualified path to the directory that contains the desired tests, or click and select the test directory in the dialog that opens. This field is only available, when the All tests in folder scope is selected.|
|Test file name mask||Specify the mask of the test file name, for example:
This field is only available, when the All tests in folder scope is selected.
|Ruby script||Type the fully qualified path to the desired script in the text field, or click
and select it in the dialog that opens.
This field is only available, when the Test script scope is selected.
|Test name filter||In this field, type a filtering expression, or the name of a test method, depending on the framework in question.
The test name filter can be e regular expression.|
This field is only available, when the Test method option is selected.
|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.
|Runner options||Specify the options to be passed to the test runner.|
|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.|
|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.|
|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 |
Code Coverage tab
Use this tab to configure code coverage monitoring options.
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 |
|Enable coverage in test folders.||If this check box is selected, the folders marked as test are included in the code coverage analysis.|
|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, RubyMine analyzes the running processes, and does one of the following, depending on the presence of the running Nailgun server:
If this check box is not selected, then the script is launched in a usual way, without Nailgun.
|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. The button is available only when an entry is selected.|
|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.|
|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.
The shared run/debug configurations are kept in separate xml files under
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 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 must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.