[ 
https://issues.apache.org/jira/browse/FLINK-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560895#comment-17560895
 ] 

Martijn Visser edited comment on FLINK-20392 at 6/30/22 8:18 AM:
-----------------------------------------------------------------

[~wangyang0918] I think we're open for anything. Are there already best 
practices when it comes to running these type of tests that we could adopt? Is 
everyone still using Bash based tests? 

Edit: did a little bit of searching; shouldn't we use things like 
https://github.com/kubernetes-sigs/kubetest2 ? 


was (Author: martijnvisser):
[~wangyang0918] I think we're open for anything. Are there already best 
practices when it comes to running these type of tests that we could adopt? Is 
everyone still using Bash based tests? 

> 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: Major
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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)

Reply via email to