Run/Debug Configuration: Arquillian TestNG
- 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
Arquillian Container tab
See also, Arquillian Containers.
This tab lets you specify the settings for TestNG.
|All in package||Run all tests in a package. |
In single module. IntelliJ IDEA will look for the tests only in the module that is selected in the Use classpath of module field.
|Suite||Run a test suite.|
|Group||Run a test group. |
Group. The group to be run. Learn more about TestNG groups.
|Class||Run a test class.|
|Method||Run a test method.|
|Pattern||Run the tests that conform to the specified pattern.|
|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 the 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.|
|Properties file||Specify the |
|Name - Value||Additional paramenters 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 code coverage runner||Select the desired code coverage runner.|
|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 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 pop-up window. |
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.|
|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. |
Each pattern can be enabled or disabled. To do that, select or clear the checkbox 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 checkbox to enable the option |
|Enable coverage in test folders.||If this checkbox is selected, the folders marked as test are included in the code coverage analysis.|
If this checkbox is not selected, IntelliJ IDEA will use the coverage tool included in the selected Python interpreter.
Refer to the section Code Coverage for details.
|Is Active||Select checkboxes 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 checkbox to have the previous content of the selected log skipped.|
|Save console output to file||Select this checkbox 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 checkbox 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 checkbox 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.
|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.