Run/Debug Configuration: JRuby Cucumber
The dialog consists of the following tabs:
Configuration tab
Item | Description |
|---|---|
Mode | Click one of the radio buttons to define the scope of features:
|
Feature folder | Specify the fully qualified path to the directory that contains the desired features, or click |
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 | RubyMine will execute the feature elements with the names that contain matching substrings |
Tags filter | Specify the tags to be considered on running tests |
Runner options | Enter runner options. |
VM options | Specify the string to be passed to the VM for launching an application, for example, When specifying JVM options, follow these rules:
The |
Working directory | Specify the working directory used by the running task. For example, this option is in effect when the running script loads other scripts by relative paths. |
Environment variables | Specify the list of environment variables as the name-value pairs, separated with semi-colons. Alternatively, click Formerly, the environment variable Now this setting is not used any more. If defining the environment variable |
Ruby arguments | Specify the command-line arguments to be passed to the Ruby interpreter. |
Ruby SDK | Specify the desired Ruby interpreter. You can choose the project default Ruby SDK, or select a different one from the list of configured Ruby SDKs. |
Use classpath of module | Select the module whose classpath should be used to run the application. |
Item Description Main class Specify the fully qualified name of the class with the By default, the main class name is Type the class name manually or click Glue In this text field, specify the name of the package, where step definitions are stored. VM options Specify the string to be passed to the VM for launching an application, for example, When specifying JVM options, follow these rules: Use spaces to separate individual options, for example, If an option includes spaces, enclose the spaces or the argument that contains spaces in double quotes, for example, If an option includes double quotes (as part of the argument), escape the double quotes using backslashes, for example, You can pass environment variable values to custom Java properties. For example, if you define a variable The Program arguments Type a list of arguments to be passed to the program in the format you would use on the command line. Use the same rules as for specifying the VM options. Working directory Specify the working directory to be used for running the application. 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 Expand the list to view available path variables that you can use as a path to your working directory. Environment variables Create environment variables and specify their values. Use classpath of module Select the module whose classpath should be used to run the application. Shorten command line Select a method that will be used to shorten the command line if the classpath gets too long, or you have many VM arguments that exceed your OS command line length limitation: none: RubyMine will not shorten a long classpath. If the command line exceeds the OS limitation, RubyMine will be unable to run your application and will display a message suggesting you to specify the shortening method. JAR manifest: RubyMine will pass a long classpath via a temporary classpath.jar. The original classpath is defined in the manifest file as a classpath file: RubyMine will write a long classpath into a text file. Use this tab to configure code coverage monitoring options. Item Description Click this button to define the scope of code coverage analysis. In the Add Pattern dialog 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 checkbox 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 checkbox to enable the option Enable coverage in test folders If this checkbox is selected, the folders marked as test 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 checkboxes 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. 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 checkbox to have the previous content of the selected log skipped. Save console output to file Select this checkbox 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 checkbox 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 checkbox 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. When you edit a run configuration (but not a run configuration template), you can specify the following options: Name Specify a name for the run configuration to quickly identify it among others when editing or running. Allow multiple instances Allow running multiple instances of this run configuration in parallel. By default, it is disabled, and when you start this configuration while another instance is still running, RubyMine suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances. Store as project file Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. By default, it is disabled, and RubyMine stores run configuration settings in .idea/workspace.xml. 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. The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent. 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 Then, to move a configuration into a folder, between the folders or out of a folder, use drag or To remove grouping, select a folder and click Click this button to sort configurations in the alphabetical order. In this area, you can specify tasks to 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: Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in RubyMine yet, add its definition. For more information, see External tools and External Tools. Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration. Run File Watchers: select this option to have RubyMine apply all the currently active File Watchers. Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog 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 Gulp task. In the Gulp task dialog 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 option to execute an npm script. In the NPM Script dialog that opens, specify the npm run/debug configuration settings. Start React Native Bundler: select this option to run the bundler automatically, as part of a running or debugging session. By default, this is done through If your application uses Expo, you need to run the development server via the Compile TypeScript: select 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 checkbox to configure the behaviour of the compiler in case any errors are detected: If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start. If the Check errors checkbox 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 generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located. 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. Run Remote External Tool: adds a remote SSH external tool. Run Rake task: add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button Note that code completion is available here. Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any). 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 By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.Configuration tab
main() method. This class is taken from the jar archive attached when enabling Cucumber support in project.cucumber.cli.Main.
to open the Choose Main Class dialog, where you can find the desired class by name or search through the project.-mx, -verbose, and so on.-client -ea -Xmx1024m.some" "arg or "some arg".-Dmy.prop=\"quoted_value\".MY_ENV_VAR, you can pass it to the foo property as follows: -classpath option specified in this field overrides the classpath of the module. and select the directory.class-path attribute in classpath.jar. You will be able to preview the full command line if it was shortened using this method, not just the classpath of the temporary classpath.jar.Code Coverage tab
--no-rcovrt. Use this option with discretion, since it significantly slows down performance.
are included in the code coverage analysis.Logs tab
Common settings
Toolbar
, and specify the folder name. If only a category is in focus, an empty folder is created.
and 
buttons..
Before launch
react-native start. start npm task. To do that, click , then in the Configure React Native dialog, choose npm script and select start from the list., and select the desired task from the list of available tasks.
/