[SUREFIRE-2075] Implementation of TestNG "threadCount" option improperly overrides default value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-M7
• Component/s: TestNG support
• Assignee: Slawomir Jaranowski
• Reporter: Scott Babcock
• Created: 20/Apr/22 16:51
• Updated: 25/May/22 05:37
• Resolved: 25/May/22 05:37

Description

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, 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.

Issue Links

• links to: GitHub Pull Request #528