[
https://issues.apache.org/jira/browse/SUREFIRE-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Falko Modler updated SUREFIRE-1196:
-----------------------------------
Description:
While analyzing a test failure, I wanted to execute a couple of tests in a
specific order via {{-Dtest=...}} to rule out any data interferences between
the tests involved.
But I missed the fact that the list of tests is just used as an include filter
(and disables any excludes). The {{runOrder}} (alphabetical",
"reversealphabetical", "random", "hourly", "failedfirst", "balanced" or
"filesystem") kicks in making it impossible to enforce the execution order.
*Suggestions for a solution*
- introduce {{runOrder}} "predefined" which can be combined with {{test}}
- or introduce a new parameter like
{{surefire.testInOrder=SomeTest,AnotherTest,...}}
was:
While analyzing a test failure, I wanted to execute a couple of tests in a
specific order via {{-Dtest=...}} to rule out any data interferences between
the tests involved.
But I missed the fact that the list of tests is just used as an include filter
(and disables any excludes). The {{runOrder}} (alphabetical",
"reversealphabetical", "random", "hourly", "failedfirst", "balanced" or
"filesystem") kicks in making it impossible to enforce the execution order.
*Suggestions for a solution*
- introduce {{runOrder}} "predefined" which can be combined with {{test}}
- or introduce a new parameter like {{surefire.testInOrder}}
> User defined run order via -Dtest=...
> -------------------------------------
>
> Key: SUREFIRE-1196
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1196
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.18.1
> Reporter: Falko Modler
>
> While analyzing a test failure, I wanted to execute a couple of tests in a
> specific order via {{-Dtest=...}} to rule out any data interferences between
> the tests involved.
> But I missed the fact that the list of tests is just used as an include
> filter (and disables any excludes). The {{runOrder}} (alphabetical",
> "reversealphabetical", "random", "hourly", "failedfirst", "balanced" or
> "filesystem") kicks in making it impossible to enforce the execution order.
> *Suggestions for a solution*
> - introduce {{runOrder}} "predefined" which can be combined with {{test}}
> - or introduce a new parameter like
> {{surefire.testInOrder=SomeTest,AnotherTest,...}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
