[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443059#comment-13443059
]
Robert Muir commented on LUCENE-4332:
-------------------------------------
Uwe I agree there is some risk, but I think we should set it up in the build to
get started
(maybe someone volunteers to run it in a sandbox'ed jenkins once a week, or
whatever).
it doesnt hurt anything to set it up in build.xml: though I agree we should
instead use
an ivy:cachepath instead of introducing so many third party dependencies for a
task/tool
that our actual codebase doesn't rely on.
I also agree tests should somehow be rerun with the same seed thru this thing.
maybe the
ant task for this can just generate a random seed itself, and pass that with a
-D.
eventually once someone gets it going, i'm sure some tuning will take place,
e.g. it should
be necessary to set parameters to ignore MMapDirectory etc (wrong file to use
mutation testing with, sorry).
> Integrate PiTest mutation coverage tool into build
> --------------------------------------------------
>
> Key: LUCENE-4332
> URL: https://issues.apache.org/jira/browse/LUCENE-4332
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 4.1, 5.0
> Reporter: Greg Bowyer
> Assignee: Greg Bowyer
> Labels: build
> Attachments:
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch,
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch
>
>
> As discussed briefly on the mailing list, this patch is an attempt to
> integrate the PiTest mutation coverage tool into the lucene build
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
