[
https://issues.apache.org/jira/browse/SUREFIRE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804945#comment-14804945
]
Jan Dundáček commented on SUREFIRE-1177:
----------------------------------------
<configuration>
<properties>
<suitethreadpoolsize>3</suitethreadpoolsize>
</properties>
...
</configuration>
... this configuration of Surefire doesn't work up to the version 6.9.6
(current version) of TestNG.
With TestNG 6.9.7-SNAPSHOT version it is ok (tested 14.9.2015), because I have
fixed it in deprecated TestNG configure method:
see https://github.com/cbeust/testng/pull/801
But the initial problem (see description) of using TestNG deprecated configure
method remains ...
> TestNG "suitethreadpoolsize" parameter can not be set by Maven Surefire
> -----------------------------------------------------------------------
>
> Key: SUREFIRE-1177
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1177
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.18.1
> Reporter: Jan Dundáček
>
> Because of Surefire is using deprecated TestNG.configure(Map) method,
> parameter "suitethreadpoolsize" value is not read by TestNG. And so test
> suites can not be run in parallel. This parameter is read only in
> TestNG.configure(CommandLineArgs) method.
> /**
> * This method is invoked by Maven's Surefire to configure the runner,
> * do not remove unless you know for sure that Surefire has been updated
> * to use the new configure(CommandLineArgs) method.
> *
> * @deprecated use new configure(CommandLineArgs) method
> */
> @Deprecated
> public void configure(Map cmdLineArgs) {
> ....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
