[
https://issues.apache.org/jira/browse/FLINK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846857#comment-17846857
]
Muhammet Orazov commented on FLINK-20392:
-----------------------------------------
[~mapohl] yes, I agree I think it is good balance, let's keep both options. We
initially was opting to keep them consistent but we can come back to it again
if that is issue again.
Migrating them into dockerized tests will add some overhead since each suite
will create (2-5) containers, wait until they are ready and terminate at the
end. At some point later we can invest some time to group tests that can reuse
the Flink cluster, testcontainers have the `reuse` option.
> 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)
