[DRILL-5318] Create a sub-operator test framework

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.0
• Fix Version/s: 1.11.0
• Component/s: Tools, Build & Test
• Labels: ready-to-commit
• Assignee: Paul Rogers
• Reporter: Paul Rogers
• Reviewer: Sorabh Hamirwasia
• Created: 07/Mar/17 17:22
• Updated: 25/Apr/17 17:16
• Resolved: 21/Apr/17 23:39

Description

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.

Issue Links

• links to: GitHub Pull Request #788

Sub-Tasks

• Refactor FragmentContext and OptionManager for unit testing: Resolved
• Refactor OptionManager for unit testing: Resolved
• Refactor FragmentContext for unit testing: Resolved
• Provide an OperatorFixture for sub-operator unit testing setup: Resolved
• Provide test tools to create, populate and compare row sets: Resolved
• Provide simplified column reader/writer for use in tests: Resolved