You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/05/18 13:53:12 UTC

[jira] [Updated] (FLINK-3656) Rework TableAPI tests

     [ https://issues.apache.org/jira/browse/FLINK-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Hueske updated FLINK-3656:
---------------------------------
    Description: 
The Table API tests are currently quite inefficient. It is mostly integration tests, partially testing the same functionality several times.

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
- duplicate tests are completely removed



  was:We should look into whether we could rework the Table API tests to extract check of Table API parts that are common for DataSet and DataStream.


> Rework TableAPI tests
> ---------------------
>
>                 Key: FLINK-3656
>                 URL: https://issues.apache.org/jira/browse/FLINK-3656
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API
>            Reporter: Vasia Kalavri
>
> The Table API tests are currently quite inefficient. It is mostly integration tests, partially testing the same functionality several times.
> 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
> - duplicate tests are completely removed



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