Run/Debug Configuration: Arquillian JUnit

If the checkbox is not selected, the run configuration settings are stored in .idea/workspace.xml or the .iws file.

If the checkbox is selected, the settings are stored in a separate xml file in .idea/runConfigurations or in the .ipr file.

See Projects.

Select where in your project IntelliJ IDEA shall look for test classes related to the current package:

• In whole project: IntelliJ IDEA will look for test classes in all project modules

• In single module: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field

• Across multiple dependencies: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field, and in the modules that depend on it

Specify the required classes using regular expressions. Each class in this field must be represented by its fully qualified name. Class names must be separated with ||. You can type class names manually, or click on the right (or press Shift+Enter) and search for classes you want to add in the dialog that opens.

For example, if you want to exclude all integration tests that have IT in their names, type ^(?!.*IT.*).*$.

You can also create a suite test, that is, a bundle of several test classes that will be run together. To create a suite test class, click on the right and type the test classes you want to be run as a suite in the Configure suit tests dialog that opens. As a result, a new class will be created with the @Suite annotation.

Select where in your project IntelliJ IDEA shall look for test classes related to the current package:

• In whole project: IntelliJ IDEA will look for test classes in all project modules

• In single module: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field

• Across multiple dependencies: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field, and in the modules that depend on it

Select this option to run all tests in a class.

Fill in the following field:

Select this option to run an individual test method.

Fill in the following fields:

Select this option if you only want to run test classes and test methods that are annotated either with the category given with the @IncludeCategory annotation, or a subtype of this category. Learn more about JUnit categories.

Fill in the following fields:

Select where in your project IntelliJ IDEA shall look for test classes related to the current package:

• In whole project: IntelliJ IDEA will look for test classes in all project modules

• In single module: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field

• Across multiple dependencies: IntelliJ IDEA will look for test classes only in the module selected in the Use classpath of module field, and in the modules that depend on it

Select this option to include classes and methods tagged with the @Tag annotation in the testing scope.

Tag expressions are boolean expressions with the following allowed operators: ! (not), & (and), and | (or). Parentheses can be used to adjust for operator precedence. For more information and examples, refer the JUnit 5 documentation.

This option controls how many Java VMs will be created if you want to fork some tests. Select method or class to create a separate virtual machine for each method or class respectively.

The available options in this list depend on the Test kind setting.

If necessary, specify the string to be passed to the VM. This string may contain the options such as -mx, -verbose, and so on.

When specifying JVM options, follow these rules:

• Use spaces to separate individual options, for example, -client -ea -Xmx1024m.

• If an option includes spaces, enclose the spaces or the argument that contains spaces in double quotes, for example, some" "arg or "some arg".

• If an option includes double quotes (as part of the argument), escape the double quotes using backslashes, for example, -Dmy.prop=\"quoted_value\".

• You can pass environment variable values to custom Java properties. For example, if you define a variable MY_ENV_VAR, you can pass it to the foo property as follows:

  -Dfoo=${MY_ENV_VAR}

If there is not enough space, you can click and enter the string in the dialog that opens.

The -classpath option specified in this field overrides the classpath of the module.

In this field, 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 required arguments in the dialog that opens.

Use the same rules as for specifying the VM options.

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.

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.

Select this checkbox to detect lines covered by one test and all tests covering line. If this checkbox is selected, becomes available on the toolbar of the coverage statistic popup.

Refer to the section Set coverage in run configurations.

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.

Name

Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10.

Allow parallel run

Select to 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, IntelliJ IDEA suggests to stop the running instance and start another one. This is helpful when a run/debug 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 IntelliJ IDEA stores run configuration settings in .idea/workspace.xml.

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 the 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 or and buttons.

To remove grouping, select a folder and click .

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 IntelliJ IDEA yet, add its definition. For more information, see External tools and External Tools.

• Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.

• Build: select to compile the specified module. The Build Module command will be executed.

  If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.

• Build Project: select to compile the entire project. The Build Project command will be executed.

  If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.

• Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results.

• Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.

• Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger.

• Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run.

• 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 Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run.

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

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

• 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 , and select the desired task from the list of available tasks.

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

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.