drill-issues 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] (DRILL-5318) Create a sub-operator test framework
Date Thu, 20 Apr 2017 16:02:04 GMT

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

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

Github user sudheeshkatkam commented on the issue:

    https://github.com/apache/drill/pull/788
  
    I am confused by your comment. Which should be committed first, 5318 or 5323? Your comments
says 5318, but the commit message for 5318 and the fact that 5318 is based on 5323 suggests
5323 should be committed first?
    
    Please format the commit message in 70fdc88 so it starts with "DRILL-XXXX: ..."


> Create a sub-operator test framework
> ------------------------------------
>
>                 Key: DRILL-5318
>                 URL: https://issues.apache.org/jira/browse/DRILL-5318
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Tools, Build & Test
>    Affects Versions: 1.11.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>              Labels: ready-to-commit
>             Fix For: 1.11.0
>
>         Attachments: Sub-OperatorTestFramework.pdf
>
>
> Drill provides two unit test frameworks for whole-server, SQL-based testing: the original
{{BaseTestQuery}} and the newer {{ClusterFixture}}. Both use the {{TestBuilder}} mechanism
to build system-level functional tests that run queries and check results.
> Jason provided an operator-level test framework based, in part on mocks: 
> As Drill operators become more complex, we have a crying need for true unit-level tests
at a level below the whole system and below operators. That is, we need to test the individual
pieces that, together, form the operator.
> This umbrella ticket includes a number of tasks needed to create the sub-operator framework.
Our intention is that, over time, as we find the need to revisit existing operators, or create
new ones, we can employ the sub-operator test framework to exercise code at a finer granularity
than is possible prior to this framework.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message