Issue Overview
In the issue #278 , there was introduced an option of delegating test execution to custom provider specified in Surefire's dependencies. But this works only for one provider. If there are more providers specified, ST picks only the first one and delegates the execution to it.
The task for this issue is to delegate the classpath scan and the test execution to multiple surefire providers (if they are present in the list of Surefire's dependencies)
A concrete example is:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.20.1</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-testng</artifactId>
<version>2.20.1</version>
</dependency>
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-junit47</artifactId>
<version>2.20.1</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>The test execution should be delegated to both providers, not only the first one.
Issue Overview
In the issue #278 , there was introduced an option of delegating test execution to custom provider specified in Surefire's dependencies. But this works only for one provider. If there are more providers specified, ST picks only the first one and delegates the execution to it.
The task for this issue is to delegate the classpath scan and the test execution to multiple surefire providers (if they are present in the list of Surefire's dependencies)
A concrete example is:
The test execution should be delegated to both providers, not only the first one.