Hi,
We apply the emma plugin via subprojects closure for our builds. This
results in seperate reports for every subproject. As you may noticed
there are some limitations here. Using emma this way means, that for
each subproject, just the classes of the subprojects itself is
instrumented and tracked. This means, that tests in ProjectB that has
dependencies to ProjectA, doesn't track potential calls on classes of
ProjectA. On the one hand this is a real limitation of the emma plugin,
on the other hand it forces you to put your unit tests where they should
be and write real UNIT tests.
For integration tests it would be nice to have this fixed. Maybe I spend
some time on this problem within the next days.
regards,
René
Am 29.01.11 02:27, schrieb Roger Studner:
> Hi Rene. I actually was just going through your various gradle plugins from
> git hah.
>
> Maybe it is simply because all my googling led me to believe people hadn't
> quite gotten it to work right yet.
>
> If I apply your plugin in the:
>
> allprojects {
> }
>
> or subprojects {
> }
>
> section of my master/main build file.. and do gradle test
>
> does it product reports for ALL the subprojects at one time?
>
> Thanks
> Roger
>
> On Jan 28, 2011, at 8:18 PM, Rene Groeschke wrote:
>
>> Hi Roger,
>> we use emma in a multiproject build. What for problems do you have or
>> googled?
>>
>> regards,
>> René
>>
>> Am 29.01.11 02:16, schrieb Roger Studner:
>>> Was curious (i've looked at the emma plugin, and the cobertura cookbook
>>> examples).... and i've googled around a bit....
>>>
>>> but I haven't yet found a successful example of doing either against a
>>> multi-module build.
>>>
>>> The geb build has some nice stuff for clover, but i'm not certain "the
>>> powers that be" are going to fork over $1500 bucks before I can prove the
>>> usefulness hah
>>>
>>> Anyone got this working?
>>>
>>> Best,
>>> Roger
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> --
>> ------------------------------------
>> Rene Groeschke
>>
>> [email protected]
>> http://www.breskeby.com
>> http://twitter.com/breskeby
>> ------------------------------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
