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-1363) Categorise unit tests by 'test-commit', 'full-test' etc
Date Thu, 28 Sep 2017 23:00:25 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-1363:

Github user afine commented on the issue:

    verified that jenkins is running the same number of tests with this patch as it did before.
The list of slow tests also appears to be reasonable. 
    small nitpick, wouldn't it make more sense to have a test category called "fast" and use
an exclusion list rather than include special logic for "slow"?

> Categorise unit tests by 'test-commit', 'full-test' etc
> -------------------------------------------------------
>                 Key: ZOOKEEPER-1363
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1363
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: build, tests
>            Reporter: Henry Robinson
>            Assignee: Mark Fenes
>              Labels: newbie
> As discussed on the list, it would be good to split the Java test suite into categories
so that it's easy to run a small set of unit tests against a patch, and to leave Jenkins to
run the full suite of stress tests etc. 

This message was sent by Atlassian JIRA

View raw message