You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/07/29 07:36:08 UTC

[jira] [Updated] (FLINK-13525) Improve Expression validation test

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

Konstantin Knauf updated FLINK-13525:
-------------------------------------
      Labels:   (was: auto-closed)
    Priority: Not a Priority  (was: Minor)

> Improve Expression validation test
> ----------------------------------
>
>                 Key: FLINK-13525
>                 URL: https://issues.apache.org/jira/browse/FLINK-13525
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>            Reporter: Jark Wu
>            Priority: Not a Priority
>
> Currently, the expression validation tests under {{org.apache.flink.table.expressions.validation}} are using following pattern to verify an exception should be thrown:
> {code:scala}
> @Test
>   def testWrongKeyType(): Unit = {
>     testAllApis('f2.at(12), "f2.at(12)", "f2[12]", "FAIL")
>   }
> {code}
> However, this only covers the first expression {{'f2.at(12)}} throw the expected exception. All the other expression will be ignored. We should improve this. And it's nice to test the expected exception message too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)