[
https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921866#action_12921866
]
Justin Edelson commented on SLING-1803:
---------------------------------------
committed initial version of this in r1023522.
to run it, from the root:
mvn -P test-reactor-sling-bundles -P emma clean install && mvn -P emma-report
validate
this still needs some tuning. I don't like that the emma report has to be done
in a separate execution of Maven, but this has to be done because emma uses a
shutdown hook to write coverage data to the coverage.ec file. The answer to
this might be to have launchpad:start fork a separate VM, which launchpad:stop
will kill.
There's also some extraneous packages in the coverage data (org.felix.*,
org.slf4j.*, o.a.sling.commons.testing.*, the installer its).
All that said, it does work and after running the command above, coverage
reports are in /coverage/.
> add coverage reporting of integration tests
> -------------------------------------------
>
> Key: SLING-1803
> URL: https://issues.apache.org/jira/browse/SLING-1803
> Project: Sling
> Issue Type: New Feature
> Components: Launchpad
> Reporter: Justin Edelson
> Assignee: Justin Edelson
>
> I've tried both emma and clover. Looks like emma is the right choice as it is
> a little more flexible in terms of breaking apart the instrumentation from
> the test execution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
