Run/Debug Configuration: Arquillian TestNG
Arquillian TestNG run/debug configurations let you run and debug your Arquillian TestNG tests. (The JBoss Arquillian Support plugin must be enabled.)
- Name, Share, and Single instance only
- Arquillian Container tab
- Configuraion tab
- Code Coverage tab
- Logs tab
- Before Launch options
See also, Arquillian: a Quick Start Guide.
Name, Share, and Single instance only
|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.
This tab lets you specify the settings for TestNG.
|All in package||Run 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.
|Suite||Run a test suite. |
Suite. Specify the corresponding
|Group||Run a test group. |
Group. The group to be run. Learn more about TestNG groups.
|Class||Run a test class. |
Class. The fully qualified name of the test class to be run.
|Method||Run a test method. |
Class. The fully qualified name of the test class.
Method. The name of the method to be run.
|Pattern||Run the tests that conform to the specified pattern. |
Pattern. Form the pattern by clicking and then selecting one or more TestNG test classes. Alternatively, click and type the pattern in the dialog that opens.
|Output directory||The directory in which test reports will be generated.|
|VM options||Options and arguments to be passed to the JVM in which the tests run. |
When specifying JVM options, follow these rules:
|Test runner parameters||Arguments to be passed to the test runner. |
Use the same rules as for specifying the VM options.
|Working directory||The current working directory for the tests.|
|Environment variables||The environment variables to be passed to the corresponding JVM.|
|Use classpath of module||The module whose classpath is used when running the tests.|
|JRE||The 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: |
|Properties file||Specify the |
|Name - Value||Additional parameters as key - value pairs.|
|Use these icons to make up a list of listeners.|
Code Coverage tab
Use this tab to configure code coverage monitoring options.
|Choose 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.
Refer to the section : view JUnit tests that cover the line at caret. .
|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.|
|Enable coverage in test folders.||If this check box is selected, the folders marked as test are included in the code coverage analysis.|
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 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.|
Before Launch options
Specify which tasks should be carried out before starting the run/debug configuration.
|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.
|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.