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

Francesco Guardiani commented on FLINK-25809:
---------------------------------------------

I won't have time to work on this anymore unfortunately. I had a couple of 
ideas in mind, so here is my WIP for who wants to take this over: 
[https://github.com/slinkydeveloper/flink/tree/upgrade-tests] . Note that the 
branch is quite old, and in the meantime we have reworked a couple of things, 
starting from the MiniClusterExtension, so this definitely needs a lot of work.

> Introduce test infra for building FLIP-190 tests 
> -------------------------------------------------
>
>                 Key: FLINK-25809
>                 URL: https://issues.apache.org/jira/browse/FLINK-25809
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Francesco Guardiani
>            Assignee: Francesco Guardiani
>            Priority: Major
>
> The FLIP-190 requires to build a new test infra. For this test infra, we want 
> to define test cases and data once, and then for each case we want to execute 
> the following:
> * Integration test that roughly does {{create plan -> execute job -> trigger 
> savepoint -> stop job -> restore plan -> restore savepoint -> execute job -> 
> stop and assert}}. Plan and savepoint should be commited to git, so running 
> this tests when a plan and savepoint is available will not regenerate plan 
> and savepoint.
> * Change detection test to check that for the defined test cases, the plan 
> hasn't been changed. Similar to the existing {{JsonPlanITCase}} tests.
> * Completeness of tests/Coverage, that is count how many times ExecNodes 
> (including versions) are used in the test cases. Fail if an ExecNode version 
> is never covered.
> Other requirements includes to "version" the test cases, that is for each 
> test case we can retain different versions of the plan and savepoint, in 
> order to make sure that after we introduce a new plan change, the old plan 
> still continues to run



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to