Run/Debug Configuration: Arquillian JUnit
Arquillian JUnit run/debug configurations let you run and debug your Arquillian JUnit tests. (The JBoss Arquillian Support plugin must be enabled.)
- Name, Share, and Single instance only
- Arquillian Container tab
- Configuration tab
- Code Coverage tab
- Logs tab
- Before Launch options
- Toolbar
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 If the checkbox is selected, the settings are stored in a separate |
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.
Configuration tab
This tab lets you specify the settings for JUnint.
Item | Description | |
---|---|---|
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:
| |
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 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 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 | |
Method | Specify the method to be launched (passed to the JRE). Type method name, or click 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:
| |
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 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 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 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 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:
| |
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 JVM options, follow these rules:
If there is not enough space, you can click and enter the string in the dialog that opens. The | |
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 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 and select the desired directory in the dialog that opens. You can also click to switch between directories. | |
Environment variables | Click 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 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.
Item | Description |
---|---|
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. |
Sampling | Select this option to measure code coverage with minimal slow-down. |
Tracing | Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only. |
Track per test coverage | Select this check box to detect lines covered by one test and all tests covering line. If this check box is selected, 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 results | When 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 data | Click and 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 button. |
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 --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 are included in the code coverage analysis. |
coverage.py
.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.
Item | Description |
---|---|
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 a message is printed to standard output stream | Select 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 stream | Select this check box 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. |
Before Launch options
Specify which tasks should be carried out before starting the run/debug configuration.
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Click this icon to add a task to the list. Select the task to be added, for example:
| |
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 | 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. |
Toolbar
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Create a run/debug configuration. | |
Alt+Delete | Delete the selected run/debug configuration. | |
Ctrl+D | Create a copy of the selected run/debug configuration. | |
View and edit the default settings for the selected run/debug configuration. | ||
Alt+Up/Alt+Down | 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 in the corresponding list on the main toolbar. | |
You can group run/debug configurations by placing them into folders. To create a folder, select the configurations to be grouped and click . Specify the name of the folder. Then, to move a configuration into a folder, between the folders or out of a folder, use and . You can also drag a configuration into a folder. To remove grouping, select a folder and click . See also, Creating Folders and Grouping Run/Debug Configurations. |