[
https://issues.apache.org/jira/browse/FLINK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240549#comment-17240549
]
Yang Wang commented on FLINK-20392:
-----------------------------------
[~mapohl] Thanks for creating this umbrella ticket to track all the migration.
It is really a good start point.
For the Junit based tests, I think it will be great if we use the testcontainer
to run. However, for some e2e tests which depends on some external system(e.g.
minikube), I am not sure how to migrate them to Java based framework. Could we
expect that the external system is already running there before running the e2e
test? Maybe it could be started by script or azure pipeline. An alternative is
we wrap the start/stop into the Java code and call it for each test.
> Migrating bash e2e tests to Java/Docker
> ---------------------------------------
>
> Key: FLINK-20392
> URL: https://issues.apache.org/jira/browse/FLINK-20392
> Project: Flink
> Issue Type: Test
> Components: Test Infrastructure, Tests
> Reporter: Matthias
> Priority: Major
>
> 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.3.4#803005)
