[FLINK-5270] Refactor the batch Scala-expression Table API tests

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.4.0
• Component/s: Table SQL / API
• Assignee: sunjincheng
• Reporter: Fabian Hueske
• Created: 07/Dec/16 10:41
• Updated: 16/Nov/17 10:40
• Resolved: 16/Nov/17 10:40

Description

Most tests of the batch Scala Table API tests are full-blown integration tests which are rather expensive to execute.

Most of tests should be converted into unit tests that validate the resulting execution plan (consisting of DataSetRel nodes) based on the TableTestBase class.

In addition we need a few integration tests that check the translation from the optimized DataSetRel plan to a DataSet program. These tests should be done by extending the TableProgramsCollectionTestBase (see FLINK-5268). These tests must cover the translation process of each DataSetRel operator.