You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/28 16:09:20 UTC

[jira] [Commented] (FLINK-3656) Rework Table API tests

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

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

GitHub user twalthr opened a pull request:

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

    [FLINK-3656] [table] Reduce number of ITCases

    This is the first step of reducing the number of ITCases of the Table API. This PR modifies the TableProgramsTestBase to test only the default configuration in collection execution environment. Other configurations will be enabled individually per test.
    
    It reduces the number of tests. From 955 to 403 tests.

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

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

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

    https://github.com/apache/flink/pull/2563.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 #2563
    
----
commit e13354a03fd6a1207a53894f2f58739326d804e6
Author: twalthr <tw...@apache.org>
Date:   2016-09-28T15:23:18Z

    [FLINK-3656] [table] Reduce number of ITCases

----


> 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)