[
https://jira.codehaus.org/browse/SUREFIRE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315313#comment-315313
]
Kristian Rosenvold commented on SUREFIRE-934:
---------------------------------------------
This is the stuff git was built for ;)
In general, if you have a spurious IT failure, it is best to preserve the
contents of
surefire-integration-tests/target/Surefire570MultipleReportDirectoriesIT/<testName>
and see if it's possible to understand what happened, possibly by examining
the logs/content inside that directory.
Personally I am much more troubled by ConcurrentReporterManagerTest failing
every now and then, and that's a unit test (damn it). I am trying to find out
about that....
> Remove getLocatedClasses() and size() from TestsToRun
> -----------------------------------------------------
>
> Key: SUREFIRE-934
> URL: https://jira.codehaus.org/browse/SUREFIRE-934
> Project: Maven Surefire
> Issue Type: Task
> Components: process forking
> Affects Versions: 2.13
> Reporter: Andreas Gudian
> Priority: Minor
>
> In order to avoid any further confusion with
> {{TestsToRun.getLocatedClasses()}} and {{TestsToRun.size()}} (as in
> SUREFIRE-933), I propose to remove these methods completely.
> Basically, these methods are used in the TestNG provider at some limited
> places, and in {{DefaultRunOrderCalculator}} during the scan for tests (in
> the main surefire process).
> If you have any objections, please close this issue. Otherwise, I will just
> do it and send a pull request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
