[jira] [Created] (SUREFIRE-2064) Implementation of TestNG "parallel" option fails with default value

["Scott Babcock (Jira)" <ji...@apache.org>]

Scott Babcock created SUREFIRE-2064:
---------------------------------------

             Summary: Implementation of TestNG "parallel" option fails with default value
                 Key: SUREFIRE-2064
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2064
             Project: Maven Surefire
          Issue Type: Bug
          Components: TestNG support
    Affects Versions: 3.0.0-M6
            Reporter: Scott Babcock


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:

{code:java}
[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 ) 
{code}

"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).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)