On Mon, Oct 31, 2011 at 12:27 PM, Lukas Renggli <renggli@gmail.com> wrote:

Cool, so what is your experience? Does it work well with the latest Cog?

Yes, as far as I can see yes. But it would be cool another guy test it also because there is no exact way to be sure whether it is working good or not. I just check the non-covered methods and I analyzed if they are correct not to be covered or not....
�

I should re-enable the coverage on my images again :-)

Sure, but first give it a try with a normal image with latest cog. If it works then update your jenkis :)
�

Lukas

On 31 October 2011 12:22, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
>
>>
>> You run HDCoverageReport exactly the same way as HDTestReport.
>>
>> HDCoverageReport uses exactly the same mechanism as the Test Runner to
>> figure out the code you want calculate the coverage on. That is, you
>> have to override #packageNamesUnderTest on the class side of one of
>> your test classes.
>
> Wow....I wasn't aware of that. I always trigger the TestCoverage from the
> test runner and then I needed to select the package to which it should
> calculate the coverage...
>
>>
>> I don't know if HDCoverageReport still works, because I stopped using
>> it when I started with Cog on Jenkins. It definitely works on
>> traditional VMs. Probably today it works on Cog too.
>
> Yes, latest Cog works ok with test coverage, and HDCoverageReport works!!
> look the attached screenshot
>
> Thanks Lukas
>
>
>>
>> Lukas
>>
>>
>> --
>> Lukas Renggli
>> www.lukas-renggli.ch
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>

--
Lukas Renggli
www.lukas-renggli.ch