[jira] [Commented] (SLING-1803) add coverage reporting of integration tests
[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790171#comment-13790171 ] Bertrand Delacretaz commented on SLING-1803: For now I have added a new jacoco-report profile to the Sling parent pom, http://svn.apache.org/r1530538 With this, a build that's run with -Pjacoco-report and includes tests produces a test coverage report at target/site/jacoco/index.html 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: Bertrand Delacretaz Attachments: integration-deploys-jacoco-exec.patch, jacoco-pom.patch, SLING-1803-1053340.patch 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 was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-1803) add coverage reporting of integration tests
[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623683#comment-13623683 ] Bertrand Delacretaz commented on SLING-1803: With the JaCoCo servlet introduced in SLING-2810 we have a way of getting coverage data from a Sling instance via HTTP, so we can now get that after running integration and server-side tests. JaCoCo's ant tasks provide a way to merge several data files [1] so we should now be able to get complete test coverage after a full Sling build that includes integration tests. [1] http://www.eclemma.org/jacoco/trunk/doc/ant.html#merge (looks like the Maven plugin doesn't have that feature, but worst case we can call the ant task from Maven) 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 Attachments: SLING-1803-1053340.patch 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SLING-1803) add coverage reporting of integration tests
[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922627#action_12922627 ] Justin Edelson commented on SLING-1803: --- in r1024330, disabled instrumentation profile by default. 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.
[jira] Commented: (SLING-1803) add coverage reporting of integration tests
[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
