[
https://issues.apache.org/jira/browse/FLINK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846609#comment-17846609
]
Muhammet Orazov commented on FLINK-20392:
-----------------------------------------
Thanks [~lorenzo.affetti] ,
{quote}MiniClusterExtension:
- PRO: the code is very clean: no need to deploy separate JAR for the Flink
app, as that is coded in the test and the Flink cluster is registered in the
current test environment
{quote}
I would see this also extra work as CON. Most of the e2e are already have so
called TestProgram, with MiniCluster approach these functionality will have to
extracted. I think this is extra effort, instead we could submit those test
programs to FlinkContainers and validate the expected outcome(s).
> Migrating bash e2e tests to Java/Docker
> ---------------------------------------
>
> Key: FLINK-20392
> URL: https://issues.apache.org/jira/browse/FLINK-20392
> Project: Flink
> Issue Type: Technical Debt
> Components: Test Infrastructure, Tests
> Reporter: Matthias Pohl
> Priority: Minor
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> starter
>
> This Jira issue serves as an umbrella ticket for single e2e test migration
> tasks. This should enable us to migrate all bash-based e2e tests step-by-step.
> The goal is to utilize the e2e test framework (see
> [flink-end-to-end-tests-common|https://github.com/apache/flink/tree/master/flink-end-to-end-tests/flink-end-to-end-tests-common]).
> Ideally, the test should use Docker containers as much as possible
> disconnect the execution from the environment. A good source to achieve that
> is [testcontainers.org|https://www.testcontainers.org/].
> The related ML discussion is [Stop adding new bash-based e2e tests to
> Flink|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Stop-adding-new-bash-based-e2e-tests-to-Flink-td46607.html].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
