IntelliJ IDEA 2016.3 Help

Run/Debug Configuration: Arquillian JUnit

Run | Edit Configurations | /help/img/idea/2016.3/new.png | Arquillian JUnit


Arquillian JUnit run/debug configurations let you run and debug your Arquillian JUnit tests. (The JBoss Arquillian Support plugin must be enabled.)

See also, Arquillian: a Quick Start Guide.

Name, Share, and Single instance only

Item Description
Name The name of the run configuration.
Share Select this check box to share the run configuration through version control.

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

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

See Project format and files.

Single instance only If you select this check box, only one instance of the run configuration will run at a time.

Arquillian Container tab

To configure your Arquillian containers, click Configure. Then select the container to be used.

See also, Arquillian Containers.

Configuration tab

This tab lets you specify the settings for JUnint.

ItemDescription
Test kind From this drop-down list, select the scope for your tests and fill in the fields depending on your selection.
All in package Select this option to run all unit tests in the specified package. Fill in the following fields:
Package Specify package name
Search for tests 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
All in directory Select this option to run all unit tests in the specified directory. Fill in the following field:
Directory Specify the directory where you want to run the tests. It will act as the root directory for all relative input and output paths.
Pattern Select this option to run a set of test classes. This set may include classes located in the same or different directories, packages or modules. Fill in the following fields:
Pattern Specify the required classes. 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 /help/img/idea/2016.3/new.png on the right (or press Shift+Enter) and search for classes you want to add in the dialog that opens.

You can also create a suite test, i.e. a bundle of several test classes that will be run together. To create a suite test class, click /help/img/idea/2016.3/edit_scopes_icon.png 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.

Method Specify the method to be launched (passed to the JRE). Type method name, or click /help/img/idea/2016.3/browseButton.png and select the desired method in the dialog that opens.
Search for tests 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
Class Select this option to run all tests in a class.

Fill in the following field:

Class Specify the fully qualified name of the class to be launched (passed to the JRE). Type the class name or click /help/img/idea/2016.3/browseButton.png and select the desired class in the dialog that opens.
Method Select this option to run an individual test method.

Fill in the following fields:

Class Specify the fully qualified name of the class to be launched (passed to the JRE). Type the class name or click /help/img/idea/2016.3/browseButton.png and select the desired class in the dialog that opens.
Method Specify the method to be launched (passed to the JRE). Type method name, or click /help/img/idea/2016.3/browseButton.png and select the desired method in the dialog that opens.
Category 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:

Category Specify the desired category. Type category name, or click /help/img/idea/2016.3/browseButton.png and select the desired category in the dialog that opens.
Search for tests 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
Fork mode 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 drop-down list depend on the Test kind setting.

Repeat If you want to repeatedly run a test, select the threshold from this drop-down list. You can select to run your test once, n times (in this case specify the number of times in the field on the right), until the test fails, or until it is stopped.
VM options If necessary, specify the string to be passed to the VM. This string may contain the options such as -mx, -verbose, etc.

When specifying the 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 the spaces in double quotes, for example, some" "arg or "some arg".
  • If an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".

If there is not enough space, you can click /help/img/idea/2016.3/edit_scopes_icon.png and enter the string in the dialog that opens.

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

Program arguments 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 /help/img/idea/2016.3/edit_scopes_icon.png button and type the required arguments in the dialog that opens.

Use the same rules as for specifying the VM options.

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 /help/img/idea/2016.3/browseButton.png and select the desired directory in the dialog that opens. You can also click /help/img/idea/2016.3/icon_switch_directories.png to switch between directories.

Environment variables Click /help/img/idea/2016.3/browseButton.png to open the Environment Variables dialog box where you can create variables and specify their values.
Use classpath of module Select the module whose classpath should be used to run the tests.
JRE Specify the JRE to be used. Select the JRE from the list, or click /help/img/idea/2016.3/browseButton.png and select the installation folder of the required JRE in the dialog that opens.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

ItemDescription
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 or Emma for calculating coverage.

SamplingSelect this option to measure code coverage with minimal slow-down.
TracingSelect this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverageSelect this check box to detect lines covered by one test and all tests covering line. If this check box is selected, /help/img/idea/2016.3/junitIcon.png becomes available on the toolbar of the coverage statistic pop-up window.

Refer to the section Viewing Code Coverage Results.

Merge data with previous resultsWhen 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.
Packages and classes to record code coverage dataClick add-class and add-package 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 /help/img/idea/2016.3/delete.png button.
Enable coverage in test folders.If this check box is selected, the folders marked as test /help/img/idea/2016.3/rootTest.gif 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.

ItemDescription
Is ActiveSelect 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 EntryThe 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.

Skip ContentSelect this check box to have the previous content of the selected log skipped.
Save console output to fileSelect 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 streamSelect 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 streamSelect this check box to activate the output console and bring it forward if an associated process writes to Standard.err.
/help/img/idea/2016.3/new.png 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.
/help/img/idea/2016.3/editFlexLibraryNew.png Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
/help/img/idea/2016.3/delete.png Click this button to remove the selected log entry from the list.
browseButton.png Click this button to edit the select log file entry. The button is available only when an entry is selected.

Before Launch options

Specify which tasks should be carried out before starting the run/debug configuration.

ItemShortcutDescription
/help/img/idea/2016.3/new.png Alt+Insert Click this icon to add a task to the list. Select the task to be added:
  • Run External tool. Select this option to run an application which is external to IntelliJ IDEA. In the dialog that opens, select the application or applications that should be run. If the necessary application is not defined in IntelliJ IDEA yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools.
  • Make. Select this option to compile the project.

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

  • Make, no error check. The same as the Make option but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation result.
  • 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.

    See also, Working with Artifacts.

  • Run Another Configuration. Select this option to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.
  • Run Ant target. Select this option to run an Ant target. In the dialog that opens, select the target to be run. For more information, see Ant.
  • 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.

    For more information, see CoffeeScript Support.

  • Run Maven Goal. Select this option to run a Maven goal. In the dialog that opens, select the goal to be run.

    For more information, see Maven.

  • Run Remote External Tool. Select this option to run a remote application which is external to IntelliJ IDEA. In the dialog that opens, select one or more remote applications to be run. If the necessary applications are not defined in IntelliJ IDEA yet, add their definitions. For more information, see Configuring Third-Party Tools and External Tools.
/help/img/idea/2016.3/delete.png Alt+Delete Click this icon to remove the selected task from the list.
/help/img/idea/2016.3/editFlexLibraryNew.png EnterClick this icon to edit the selected task. Make the necessary changes in the dialog that opens.
/help/img/idea/2016.3/arrowUp.png /help/img/idea/2016.3/arrowDown.pngAlt+Up/Alt+DownClick 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 pageSelect this check box to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window If this check box is selected, 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 if necessary.

Toolbar

ItemShortcutDescription
/help/img/idea/2016.3/new.pngAlt+InsertCreate a run/debug configuration.
/help/img/idea/2016.3/delete.pngAlt+DeleteDelete the selected run/debug configuration.
copyCtrl+DCreate a copy of the selected run/debug configuration.
/help/img/idea/2016.3/settings.pngView and edit the default settings for the selected run/debug configuration.
/help/img/idea/2016.3/arrowUp.png/help/img/idea/2016.3/arrowDown.pngAlt+Up/Alt+DownMove 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 in the corresponding list on the main toolbar.

/help/img/idea/2016.3/folder.pngYou can group run/debug configurations by placing them into folders.

To create a folder, select the configurations to be grouped and click /help/img/idea/2016.3/folder.png. Specify the name of the folder.

Then, to move a configuration into a folder, between the folders or out of a folder, use /help/img/idea/2016.3/arrowUp.png and /help/img/idea/2016.3/arrowDown.png. You can also drag a configuration into a folder.

To remove grouping, select a folder and click /help/img/idea/2016.3/delete.png.

See also, Creating Folders and Grouping Run/Debug Configurations.

See Also

Last modified: 7 December 2016