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

Lorenzo Affetti commented on FLINK-20392:
-----------------------------------------

[~mapohl] [~m.orazow] 

 

thanks for your wonderful comments.

The solution lies in between as many times happen :)

Sounds perfect to me.

I will head to addressing your last comments [~mapohl] 

I'll also review your PR [~m.orazow] 

 

Thank you for the fruitful conversation.

 

One last thing:

 

[~mapohl] do you think we should add my previous comment to the umbrella 
description, maybe with some rephrasing?

So that a future contributor does not need to read the entire discussion?

> 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)

Reply via email to