You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2016/09/08 16:30:21 UTC
[jira] [Updated] (FLINK-3656) Rework Table API tests
[ https://issues.apache.org/jira/browse/FLINK-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther updated FLINK-3656:
--------------------------------
Labels: starter (was: )
> 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)