Hi all At my current $DAYJOB we have been having a bit of success with an alternative coverage tool called pit-test ( http://pitest.org/). Essentially pit-test is a mutation testing tool that attempts to see how well the unit tests are able to catch alterations and regressions in the code that they aim to test; this is done by determining what code the test actually touch and then mutating that code in some fashion.
I have as such started working on seeing if I can integrate pit-test into the lucene build, the tool itself is apache licensed which solves that particular issue. The main downsides I can see is that the coverage might be different across runs due to lucenes random testing, as well as the time it takes to run coverage (~4 hours on a big bad sandy bridge machine). I have published initial results for lucene packages, core is missing because there is one test in core that does not work with pit-test currently (and as such I am currently working on getting core generated. It can be found here http://people.apache.org/~gbowyer/pitest/ <http://people.apache.org/%7Egbowyer/pitest/> Is this of interest to anyone other than myself, especially given the aggressive nature of how lucene is tested ? -- Greg
