You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/12/06 21:11:11 UTC

[jira] [Issue Comment Deleted] (SUREFIRE-756) Allow ability to capture executed random runOrder for re-play purposes

     [ https://issues.apache.org/jira/browse/SUREFIRE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana updated SUREFIRE-756:
----------------------------------
    Comment: was deleted

(was: The solution would be to use the existing "includesFile" parameter.
The excludesFile should not work together with runOrder.
The functionality "runOrder" creates file name which starts with ".surefire-" in base dir.
We can recognize the File name in the form of 
+ ".surefire-<configurationHash>" or 
+ ".surefire-*" and configurationHash will computed upon current plugin configuration.

The format for files produced by runOrder and includesFile are different, we can load only the name of the test upon regognized file patter ".surefire-*" in base dir.

Any objections to this concept?)

> Allow ability to capture executed random runOrder for re-play purposes
> ----------------------------------------------------------------------
>
>                 Key: SUREFIRE-756
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-756
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>    Affects Versions: 2.9
>            Reporter: Josh Spiewak
>            Assignee: Tibor Digana
>            Priority: Minor
>
> As a user of the runOrder=random feature, I would like to be able to capture a given ordering of tests and re-play that order, so that if a particular ordering exposes hidden dependencies between tests I can reproduce in my development environment, fix the problem, and then runs the tests again to confirm the fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)