Re: JUnitParams tests do not show coverage

[Marcin Zajączkowski]

Dnia �roda, 24 Kwietnia 2013 04:22 Nathan Green <ngr...@inco5.com> napisa�(a)

I am using the JUnitParams plugin for parameterized tests and I am not seeing any coverage when I use its parameterized behavior. (The @RunWith annotation doesn't cause a problem). I have attached a maven project

 

This is a known issue and is already fixed in SCM. See: https://code.google.com/p/pitestrunner/issues/detail?id=67

 

You can check your code with the pitest-0.30-SNAPSHOT and verify the results.

 

Marcin

 

 

that demonstrates this via the following commands:

1. mvn clean test org.pitest:pitest-maven:mutationCoverage
   
2. mvn site

The Cobertura report reflect the coverage correctly, but PIT does not pick up the JUnitParams-supplied @Parameters tests. I am not sure if the defect is in JUnitParams or PIT. Since PIT appears to work fine with JUnit's built-in parameterized runner, I suspect PIT may not be at fault.

 

My project also includes some commented elements in the POM because PIT would fail when Cobertura was running. I'm still new to PIT, so maybe I'm just doing something wrong. My build fails if I include this setting:

<avoidCallsTo>

<param>net.sourceforge.cobertura</param>

</avoidCallsTo>

 

Without that setting, I get a lot of bogus survival messages in the report. So it seems I cannot run PIT as part of the normal test phase in Maven and also use Cobertura. This is unfortunate. I attached a log from when I tried to build with the avoidCallTo setting.

 

 

--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

http://blog.solidsoft.info/ - Working code is not enough