Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-2075

Implementation of TestNG "threadCount" option improperly overrides default value

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0-M7
    • TestNG support
    • None

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            sjaranowski Slawomir Jaranowski
            scoba Scott Babcock
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment