Hi everyone, I started looking into the migration test data generation after I got confused about it in the context of the 1.16.0-rc1 voting process [1]. The release manager needs to do some manual work around adding test data for certain tests after the release is finalized (see item 15 in the "Checklist to declare the process completed" section of the documentation for creating a Flink release [2]): - Multiple tests need to get an update to the version they run on. - Tests will fail due to missing test data. The test data needs to be created in a manual process for each of the tests as well.
I'm playing around with aligning this a bit as part of FLINK-29485 [3]. Essentially, I'd like to move the general Flink version range setup into flink-test-utils. The release manager would have to update only one location instead of each test. Additionally, the junit test method implementations responsible for generating the test data would be enabled by default. I want to introduce a system property that can be used to specify the Flink version for which the data shall be generated. We can use assume to enable/disable the test data generation based on this system property. In the end, the release manager would have to change only code in a single location (instead of multiple files) and run the test suite with this system property being set once on the corresponding release branch to generate the data. WDYT? I'm curious whether I'm missing something. Best, Matthias [1] https://lists.apache.org/thread/b0295pq4qpwxg4gpnrr9rjk27zptgkcb [2] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release [3] https://issues.apache.org/jira/browse/FLINK-29485
