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

ASF GitHub Bot commented on FLINK-3656:
---------------------------------------

GitHub user twalthr opened a pull request:

    https://github.com/apache/flink/pull/2566

    [FLINK-3656] [table] Consolidate ITCases

    This PR merges ITCases that are belong together logically. It also ensures 
that all tests extend from TableProgramsTest base.
    
    It reduces the build time by 20 seconds.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/twalthr/flink FLINK-3656_STEP_2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2566.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2566
    
----
commit afe77695e852171bdff7f238e7bb5951eda5a8ac
Author: twalthr <twal...@apache.org>
Date:   2016-09-29T08:20:35Z

    Merge FilterIT/SelectIT to CalcITCases

commit 0f7f080dd058cf0fe2298d34510c6cf2a6bca09b
Author: twalthr <twal...@apache.org>
Date:   2016-09-29T09:04:34Z

    Merge FromDataSet/ToTable to TableEnvironmentITCases

commit 97b553a76f444db17dcbf734cbc043d46b1d9f9c
Author: twalthr <twal...@apache.org>
Date:   2016-09-29T09:22:16Z

    Merge aggregating ITCases

commit ed6a67058aa32d621266952f61383d61446464ed
Author: twalthr <twal...@apache.org>
Date:   2016-09-29T09:29:49Z

    All batch ITCases use TableProgramsTestBase

----


> Rework Table API tests
> ----------------------
>
>                 Key: FLINK-3656
>                 URL: https://issues.apache.org/jira/browse/FLINK-3656
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Vasia Kalavri
>              Labels: starter
>
> The Table API tests are very inefficient. At the moment It is mostly 
> end-to-end integration tests, often testing the same functionality several 
> times (Java/Scala, DataSet/DataStream).
> We should look into how we can rework the Table API tests such that:
> - long-running integration tests are converted into faster unit tests
> - common parts of DataSet and DataStream are only tested once
> - common parts of Java and Scala Table APIs are only tested once
> - duplicate tests are completely removed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to