[SUREFIRE-2064] Implementation of TestNG "parallel" option fails with default value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M6
• Fix Version/s: 2.22.3, 3.0.0-M7
• Component/s: TestNG support
• Assignee: Tibor Digana
• Reporter: Scott Babcock
• Created: 08/Apr/22 01:19
• Updated: 24/Apr/22 10:40
• Resolved: 23/Apr/22 23:42

Description

The latest release of Maven Surefire attempts to resolve an incompatibility with TestNG 7.4+, but the way the fix was implemented causes projects that don't specify parallel execution to fail:

[ERROR] There was an error in the forked process
[ERROR] Unsupported TestNG parallel setting: none ( only METHODS or CLASSES supported )
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
[ERROR] Unsupported TestNG parallel setting: none ( only METHODS or CLASSES supported ) 

"none" is the default value that gets passed in if no [parallel] setting is specified. TestNG actually supports NONE as a valid value, along with TESTS and INSTANCES. There are two deprecated values as well (TRUE and FALSE), which cause TestNG to log a warning and translate to equivalent supported values (METHODS and NONE respectively).

Issue Links

• is related to: SUREFIRE-1890 Not compatible with TestNG 7.4.0
• links to: GitHub Pull Request #517