[
https://jira.codehaus.org/browse/SUREFIRE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356173#comment-356173
]
Dan Fabulich commented on SUREFIRE-514:
---------------------------------------
I don't think I understand your comment.
1) I agree that it's not necessarily safe to run tests incrementally; I
mentioned this myself when I filed the bug. So I guess it's OK not to make it
the default (though we would probably opt-in to this behavior in our projects).
2) "It's better for us not to introduce a new configuration parameter at the
moment." Do you mean that it would be better to fix this bug later? It's been
open for six years. Or do you mean that this is a bad feature that should never
be done?
3) "So if you don't necessarily require this feature in SUREFIRE 2.x and 3.0
anymore, we can close it." This is a performance feature. When does anyone
"require" a performance feature? You can always live without it; it's just
slower.
But my point stands: just because it isn't guaranteed to be safe doesn't mean
that it's a bad feature; it could substantially improve performance on
developer boxes when/where we turn it on. If this feature shipped tomorrow, we
would want it and would use it.
> Provide a way to skip a project's tests if nothing has changed
> --------------------------------------------------------------
>
> Key: SUREFIRE-514
> URL: https://jira.codehaus.org/browse/SUREFIRE-514
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Dan Fabulich
>
> Surefire should have an "incremental" mode, perhaps enabled by default.
> We should check the timestamps of every element of the classpath (and every
> class in any classpath folder) and touch a file in "target" with that
> timestamp. If none of those files have been updated, skip tests for the
> current project.
> It definitely needs to be possible to turn this feature off, though, because
> sometimes you need to re-run tests based on external resources not on the
> classpath: deployed web servers, database schema changes, etc.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
