You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/01 01:20:00 UTC

[jira] [Commented] (DRILL-5752) Speed Up Unit Tests

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

ASF GitHub Bot commented on DRILL-5752:
---------------------------------------

Github user paul-rogers commented on the issue:

    https://github.com/apache/drill/pull/940
  
    @ilooner, thanks for the improvements. Is this PR now ready for final review and commit?
    
    Also, if all tests are enabled by default, is there a suggestion of a Maven command that developers should run normally in order to do a quick build and "smoke test"?


> Speed Up Unit Tests
> -------------------
>
>                 Key: DRILL-5752
>                 URL: https://issues.apache.org/jira/browse/DRILL-5752
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Timothy Farkas
>            Assignee: Timothy Farkas
>
> Tests can be split into categories.
> High-level categories:
> * Fast
> * Slow
> Low-level categories:
> * Vector
> * WebUI
> * Planner
> * Operator
> * Storage
> * Hive
> * JDBC
> * Kudu
> * Mongo
> * Hbase
> After the tests are categorized the Travis build can just run the fast tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)