IntelliJ IDEA 2017.3 Help

Run/Debug Configuration: Arquillian TestNG

Run | Edit Configurations | new | Arquillian TestNG

Arquillian TestNG run/debug configurations let you run and debug your Arquillian TestNG 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 checkbox to share the run configuration through version control.

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 Configuring projects.

Single instance only If you select this checkbox, 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.

Configuraion tab

This tab lets you specify the settings for TestNG.

All in packageRun all tests in a package.

Package. The fully qualified name of the package.

In whole project. IntelliJ IDEA will look for the tests in all the modules.

In single module. IntelliJ IDEA will look for the tests only in the module that is selected in the Use classpath of module field.

Across module dependencies. The same as the previous option plus the modules that depend on that module.

SuiteRun a test suite.

Suite. Specify the corresponding testng.xml file.

GroupRun a test group.

Group. The group to be run. Learn more about TestNG groups.

ClassRun a test class.

Class. The fully qualified name of the test class to be run.

MethodRun a test method.

Class. The fully qualified name of the test class.

Method. The name of the method to be run.

PatternRun the tests that conform to the specified pattern.

Pattern. Form the pattern by clicking new and then selecting one or more TestNG test classes. Alternatively, click editorIcon and type the pattern in the dialog that opens.

Output directoryThe directory in which test reports will be generated.
JDK Settings
VM optionsOptions and arguments to be passed to the JVM in which the tests run.

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:

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

Test runner parametersArguments to be passed to the test runner.

Use the same rules as for specifying the VM options.

Working directoryThe current working directory for the tests.
Environment variablesThe environment variables to be passed to the corresponding JVM.
Use classpath of module The module whose classpath is used when running the tests.
JREThe JRE to be used.
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: IntelliJ IDEA will not shorten a long classpath. If the command line exceeds the OS limitation, IntelliJ IDEA will be unable to run your application and will display a message suggesting you to specify the shortening method.
  • JAR manifest: IntelliJ IDEA will pass a long classpath via a temporary classpath.jar. The original classpath is defined in the manifest file as a class-path attribute in classpath.jar. Note that 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.
  • classpath.file: IntelliJ IDEA will write a long classpath into a text file.
  • User-local default: this legacy option is set automatically for projects created before IntelliJ IDEA version 2017.3. IntelliJ IDEA will configure this setting depending on the properties set in the ide/workspace.xml and idea.config.path/options/options.xml files.
Properties fileSpecify the .properties file to be passed to TestNG.
Name - ValueAdditional parameters as key - value pairs.
new deleteUse these icons to make up a list of listeners.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

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, junitIcon becomes available on the toolbar of the coverage statistic pop-up window.

This option is only available for the Tracing mode of code coverage measurement for the testing run/debug configurations.

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.

Finally, the line is considered covered if it is covered at least once.

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 delete button.
add 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.

delete Click this button to delete the selected pattern from the list.
edit1 Click this button to change the selected code coverage pattern.
Do not use the optimized C runtimeSelect this check box to enable the option --no-rcovrt. Use this option with discretion, since it significantly slows down performance.
Enable coverage in test folders.If this check box is selected, the folders marked as test root_Test.png are included in the code coverage analysis.
Use bundled If this check box is selected, IntelliJ IDEA will use the bundled
If this check box is not selected, IntelliJ IDEA will use the coverage tool included in the selected Python interpreter.

Refer to the section Code Coverage for details.

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.

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.
addClick this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
edit1Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
deleteClick 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.

new Alt+Insert Click this icon to add a task to the list. Select the task to be added, for example:
  • 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.
  • 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 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.
delete Alt+Delete Click this icon to remove the selected task from the list.
edit1 EnterClick this icon to edit the selected task. Make the necessary changes in the dialog that opens.
arrowUp arrowDownAlt+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 checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window If this checkbox 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.


newAlt+InsertCreate a run/debug configuration.
deleteAlt+DeleteDelete the selected run/debug configuration.
copyCtrl+DCreate a copy of the selected run/debug configuration.
settingsView and edit the default settings for the selected run/debug configuration.
arrowUparrowDownAlt+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.

folderYou can group run/debug configurations by placing them into folders.

To create a folder, select the configurations to be grouped and click folder. Specify the name of the folder.

Then, to move a configuration into a folder, between the folders or out of a folder, use arrowUp and arrowDown. You can also drag a configuration into a folder.

To remove grouping, select a folder and click delete.

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

Last modified: 12 January 2018

See Also