zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2955) Enable Clover code coverage report
Date Tue, 23 Jan 2018 20:11:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336312#comment-16336312
] 

ASF GitHub Bot commented on ZOOKEEPER-2955:
-------------------------------------------

Github user phunt commented on a diff in the pull request:

    https://github.com/apache/zookeeper/pull/443#discussion_r163363116
  
    --- Diff: build.xml ---
    @@ -1406,50 +1410,53 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
     
         <target name="test-core" depends="test-core-java, test-core-cppunit"/>
     
    +    <target name="test-coverage-java">
    --- End diff --
    
    Why do we need this given we have a "clover" target?
    
    I'm also hesitant to explicitly code that "coverage" == clover. In the past we've allowed
coverage other than clover to be used.
    
    perhaps "test-coverage-clover-java" instead?


> Enable Clover code coverage report
> ----------------------------------
>
>                 Key: ZOOKEEPER-2955
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2955
>             Project: ZooKeeper
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 3.5.3, 3.4.11
>            Reporter: Mark Fenes
>            Assignee: Mark Fenes
>            Priority: Major
>
> We have limited code coverage support in ZK. Clover for Java was running in the past
but was turned off. 
> Enable Clover code coverage report to make us more confident on the quality, stability
and compatibility of future ZK releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message