[
https://issues.apache.org/jira/browse/FLINK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823242#comment-17823242
]
Lorenzo Affetti commented on FLINK-20392:
-----------------------------------------
{quote}I'm not able to follow what you mean here. Both linked PRs are still
accessible (including its code change). Or do you mean that the code of the PR
is not present in the main repo anymore?
{quote}
Yeah, sorry, I meant that that code was moved/refactored (y)
But thank you for the clarification.
My goal here was to clarify which part of tests should rely on test containers.
For example, it could be that Flink runs in the same thread of the tests and
the dependencies (for example, Kafka) run in containers.
As far as I understood, also Flink should run in containers (y)
I was adding references to the code that enables that at the current state of
the repo.
> 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)
