[
https://issues.apache.org/jira/browse/SUREFIRE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed SUREFIRE-2075.
-----------------------------------------
Fix Version/s: 3.0.0-M7
Resolution: Fixed
> Implementation of TestNG "threadCount" option improperly overrides default
> value
> --------------------------------------------------------------------------------
>
> Key: SUREFIRE-2075
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2075
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Reporter: Scott Babcock
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.0.0-M7
>
>
> The implementation in *TestNGMapConfigurator* for the [threadCount] option
> injects a fixed default value of 1 if the plugin configuration does not
> explicitly specify this setting. This is unnecessary and undesirable, because
> TestNG provides a default value of 5 for [threadCount]. Also, this injected
> default value of 1 contradicts the Surefire
> [documentation|https://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Running_Tests_in_Parallel],
> and it results in sequential execution if any of the [parallel] modes are
> specified but [threadCount] is unspecified.
> The solution is to allow TestNG to provide the default [threadCount] value if
> the configuration omits this setting.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
