sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2430) Sqoop2: Precommit: Add test coverage reports
Date Sat, 25 Jul 2015 16:29:04 GMT

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

Jarek Jarcec Cecho updated SQOOP-2430:
    Attachment: SQOOP-2430.patch

I'm attaching patch that adds the cobertura call and compares results with a base (which is
a [separate Jenkins job|https://builds.apache.org/job/Sqoop2-cobertura/]). The patch is based
on top of SQOOP-2429 and SQOOP-2428, so it won't apply cleanly before those two gets committed.

> Sqoop2: Precommit: Add test coverage reports
> --------------------------------------------
>                 Key: SQOOP-2430
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2430
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.7
>         Attachments: SQOOP-2430.patch
> I know that reporting test coverage is not the best metric, but I think that it would
be useful to have a check in precommit hook that would warn us if the submitted patch has
significantly decreased test coverage (from whatever reason).

This message was sent by Atlassian JIRA

View raw message