[ https://issues.jboss.org/browse/JGRP-1728?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on JGRP-1728 at 11/6/13 12:56 PM: --------------------------------------------------------------------- The first implementation of this change was incorrect. The problem lies with the way in which paralleism is configured in testNG, which I summarise here: - you can specify attributes parallel= and thread-count= on the <testng/> ant task in order to control parallelism of test classes specified within the testng task itself ; - you can specify attributes parallel= and thread-count= on the <suite/> elements of the XML suite definition files to control parallelism of tests defined in the suite - the parallelism directives of the testng ant task, and the paralleism directives of the suite elements are completely independent What this means is that if you define your tests via suite definition files (as te JGroups testsuite does), then in order to control parallelism of test execution, you have to modify the parallelism directives in the suite files themselves This situation is made worse by the fact that you cannot use variable substitution in the testNGs suite files (i.e. no chance for defining a system property and then referencing that system property in the suite file, as in {noformat} <suite parallel="${parallel.methods}"/>) {noformat} So in order to configure parallelism, on the fly, we need to be able to modify or otherwise configure the suite files which are passed to the test cases. was (Author: rachmato): The first implementation of this change was incorrect. The problem lies with the way in which paralleism is configured in testNG, which I summarise here: - you can specify attributes parallel= and thread-count= on the <testng/> ant task in order to control parallelism of test classes specified within the testng task itself ; - you can specify attributes parallel= and thread-count= on the <suite/> elements of the XML suite definition files to control parallelism of tests defined in the suite - the parallelism directives of the testng ant task, and the paralleism directives of the suite elements are completely independent What this means is that if you define your tests via suite definition files (as te JGroups testsuite does), then in order to control parallelism of test execution, you have to modify the parallelism directives in the suite files themselves This situation is made worse by the fact that you cannot use variable substitution in the testNGs suite files (i.e. no chance for defining a system property and then referencing that system property in the suite file, as in <suite parallel="${parallel.methods}"/>) So in order to configure parallelism, on the fly, we need to be able to modify or otherwise configure the suite files which are passed to the test cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira