Test-suite analysis using mutation testing

[aliparsai]

Hi,
I used this software as a sample to test my mutation testing tool. now the tool is complete and I could generate a complete report on the quality of the test-suite. I thought I share the results, in case you needed it to improve your test-suite.

here's the link to results:
https://www.dropbox.com/s/w5ckz2ueuak31bz/mutated.zip?dl=0

you will find report.html there, and from there you can navigate and look into details.
if I can help with anything else, please let me know.

Ali

[tea-dragon]

We fared better than I might have expected. I'll see if I can't make at least a few improvements to honor your analysis. One suggestion for your tool's reports: line numbers for where the changes are made would be nice. Maybe the multi-line comment could just include the diff output.

[aliparsai]

I added this to TODO. yet, it's not easy, because antlr chews the file when parsing, and I had to change a lot inside antlr python runtime to just get the changed file to compile. so the line numbers I get to report are from the original file, and not from the mutant.

[tea-dragon]

Original file might be the more useful line number anyway.
On Oct 14, 2014 10:14 AM, "aliparsai" notifications@github.com wrote:

I added this to TODO. yet, it's not easy, because antlr chews the file
when parsing, and I had to change a lot inside antlr python runtime to just
get the changed file to compile. so the line numbers I get to report are
from the original file, and not from the mutant.

—
Reply to this email directly or view it on GitHub
#10 (comment).