Op donderdag 20 februari 2014 20:07:33 UTC+1 schreef Marc R. Hoffmann:
> Hallo Christine,
> 
> 
> 
> the prerequiste for code coverage analysis with EclEmma is that a 
> 
> language compiles to Java class files and that these class files have 
> 
> proper debug references to the original source files. Here are some 
> 
> example projects for Groovy, Java, Kotlin, Scala and Xtend:
> 
> 
> 
>    https://github.com/marchof/jacoco-maven-examples
> 
> 
> 
> If your transformation language gets directly compiled to Java class 
> 
> files and there is a proper Eclipse integration with the JDT model it 
> 
> should be possible to get code coverage with EclEmma.
> 
> 
> 
> Best regards,
> 
> -marc
> 
> 
> 
> 
> 
> On 2014-02-20 17:34, [email protected] wrote:
> 
> > Hello there,
> 
> > 
> 
> > My team uses a model transformation language called QVTo, which we
> 
> > develop in eclipse. Currently we have unit tests which are a jUnit
> 
> > file which specify input and expected output and the QVTo file to run,
> 
> > and then there's some Java code in there that actually runs the
> 
> > transformation.
> 
> > 
> 
> > So my question is: is it feasible to extend EclEmma to compute
> 
> > (rudimenary) code coverage and show highlighting for other languages
> 
> > in Eclipse?
> 
> > 
> 
> > It occurred to us since the functionality/GUI would be extremely
> 
> > similar to EclEmma, but the abstract syntax tree and function types
> 
> > are different.
> 
> > 
> 
> > I know EclEmma/JaCoCo support Scala, but I haven't figured out whether
> 
> > there's some special adapter code for that, or because it's so similar
> 
> > to Java it just works anyway? Basically I'm looking for advice like
> 
> > "this sounds really hard and a terrible idea" or "take a look at this
> 
> > class in the EclEmma/JaCoCo source".
> 
> > 
> 
> > Otherwise we just end up implementing an independent Eclipse plugin.
> 
> > 
> 
> > Any ideas?
> 
> > 
> 
> > Thanks in advance,
> 
> > Christine

As far as I understand, QVTo is interpreted (by libraries written in Java). I 
think the only compiled form is to XMI format, rather than Java bytecode. 
Debugging in Eclipse works nicely though. But I take it that EclEmma/JaCoCo 
would not be appropriate then?

-- 
You received this message because you are subscribed to the Google Groups 
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to