Hi Mathias: The link Rene posted is the one I followed to get mine working - thanks, Rene.
--- Tom C. On Sat, Oct 16, 2010 at 7:16 PM, Rene Groeschke <[email protected]> wrote: > Hi Matthias, > > I've shared my emma usage in a script plugin at > http://github.com/breskeby/gradleplugins/blob/master/emmaPlugin/emma.gradle > . > The implementation of this emma plugin doesn't support recording cross > project calls in multiproject build. > > Am 16.10.10 23:21, schrieb Matthias Bohlen: > > Hi Tom, > > > > would you like to share your build script with us, at least the > > section where it invokes Emma? I'd like to use it as an example for my > > own script. > > > > There is one point that is especially interesting: How do I invoke > > Emma so that it recognizes tests that come from other subprojects of > > the same multi-project build? I.E. a unit test in subproject A tests > > code that is in subproject B. How do I make Emma recognize that? > The problem is, that you have to instrument the class files of > subprojectB in the in the test section of subprojectB. Furthermore the > source files of subprojectB must be added to the report section in emma. > I'm not sure how to reference the source and class folders of other > subproject in a gradle multiproject build to achieve this. > > By the way. I don't think that it is good practice to test a subprojectA > in the tests of subprojectB. References to subprojectA should be mocked > in tests of subprojectB, shouldn't they? > > regards, > René > -- > > ------------------------------------ > 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 > > >
