PITclipse line coverage question

[Jacob Whitver]

Hello,

This is my first time posting to this group and I have been using PIT for about 6 months.  PIT is a great tool and has really helped my team expand our test coverage.  Thank you for creating PIT.

My question is with how the line/mutation coverage is calculated.  When I run PIT via the "Run As...->PIT Mutation Test" metric on the src/tests/java directory I get the following coverage metrics:

When I choose the package for that 3rd line and use "Run As... -> PIT Mutation Test" I get the following:

I understand why all of the other packages are reporting as 0% when running the package level.  What I am unclear on is why my third package is reporting as 0% for both Line Coverage and Mutation Coverage since it is clear that tests have been written for these classes? 

I am currently using PIT 0.31 and PITclipse 0.31.4.201401081810 and both are installed in Spring STS 3.4.0.RELEASE.   

Thanks again for the great tool.

Jacob Whitver

[Phil Glover]

Hi Jacob,

Thanks for using Pitclipse.

Just a couple of thoughts - can you try running the PIT mutation test at a project level and see what happens?  I think that running at a src/test and/or src/main could yield strange results if a package is present in one directory but not the other.

Let me know if this helps.

Kind regards,

Phil

[Jacob Whitver]

Phil,

Thanks for responding.  I ran PIT mutation test at the project level and there was no change.  I did notice that I am getting OUT_OF_MEMORY errors in the PIT logs:

11:47:54 AM PIT >> FINE : Exit code was - OUT_OF_MEMORY

11:47:54 AM PIT >> WARNING : Slave exited abnormally due to MEMORY_ERROR

11:47:54 AM PIT >> FINE : Setting 1 unfinished runs to MEMORY_ERROR state

11:47:54 AM PIT >> FINE : using port 8092

Is PIT using the STS/Eclipse heap or is there some other setting I need to use to increase memory?  I did increase my settings in the STS.ini file and the issue remains.  

I think this is probably why some of my tests are not running.

Thanks for creating PITclipse - it has been really helpful for our team so far.

Thanks,

[Phil Glover]

You can change the VM args in the Run Configurations.

Hope this helps.

Cheers,

Phil