jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-3828) Test code coverage monitoring using Coverall
Date Wed, 08 Mar 2017 13:12:38 GMT

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

Chetan Mehrotra resolved OAK-3828.
    Resolution: Later

> Test code coverage monitoring using Coverall
> --------------------------------------------
>                 Key: OAK-3828
>                 URL: https://issues.apache.org/jira/browse/OAK-3828
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: it
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
> Oak has a coverage profile based on jacoco. This is currently not enabled by default.
It would be good to have a CI profile with coverage enabled and collect the coverage data
over time via Coverall. Coveralls.io offers a useful interface to review what are the crytical
parts no covered in order to evaluate what tests write in order to rise up the coverage fastly
and is free for open source projects.
> For Maven based project it can be done by coveralls-maven-plugin [2] and then we can
add a nice badge for coverage!. The plugin requires a token key which can be encrypted for
Travis [3]. Most likely for Apache Jenkins we can specify the key in build setup
> [1] https://coveralls.io/
> [2] https://github.com/trautonen/coveralls-maven-plugin
> [3] https://docs.travis-ci.com/user/encryption-keys/

This message was sent by Atlassian JIRA

View raw message