You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2010/12/28 14:28:45 UTC

[jira] Updated: (SLING-1803) add coverage reporting of integration tests

     [ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-1803:
---------------------------------------

    Attachment: SLING-1803-1053340.patch

I tried running this on trunk revision 1053340, and I had to apply the attached patch. I won't commit it now as there might be a way to avoid the optional dependency.

The Drools rule change was needed to avoid an NPE when executing mvn directly from the launchpad/testing folder, but that might not make sense.

Note also that the DavExIntegrationTest fails when running with both profiles mentioned in this issue, probably a classpath problem as the failure is:

java.lang.NoSuchMethodError: javax.jcr.Session.getNode(Ljava/lang/String;)Ljavax/jcr/Node;
        at org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest.testReadNode(DavExIntegrationTest.java:60)

I haven't investigated that failure.


> 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.
-
You can reply to this email to add a comment to the issue online.