You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 17:22:00 UTC
[jira] [Resolved] (SUREFIRE-530) Allow runtime ordering of tests to
be specified
[ https://issues.apache.org/jira/browse/SUREFIRE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold resolved SUREFIRE-530.
--------------------------------------------
Resolution: Abandoned
doesn't look likely to happen
> Allow runtime ordering of tests to be specified
> -----------------------------------------------
>
> Key: SUREFIRE-530
> URL: https://issues.apache.org/jira/browse/SUREFIRE-530
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.4.3
> Environment: testNG, Junit
> Reporter: Nick Pellow
> Priority: Major
> Fix For: 3.0
>
>
> Allow other plugins to specify tests to get run, and preserve the ordering of tests.
> Currently, a plugin may set the "test" parameter with a comma separated list of tests to run.
> However, the order is not preserved.
> For plugins such as the maven-clover2-plugin, (possibly the maven-reactor-plugin?) that optimize the build/test run, ordering of a tests is a very nice way to ensure the build fails as fast as possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)