[ 
https://issues.apache.org/jira/browse/FLINK-32866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Fan updated FLINK-32866:
----------------------------
    Labels: pull-request-available starter  (was: pull-request-available 
stale-assigned starter)

> Unify the TestLoggerExtension config of junit5
> ----------------------------------------------
>
>                 Key: FLINK-32866
>                 URL: https://issues.apache.org/jira/browse/FLINK-32866
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Tests
>            Reporter: Rui Fan
>            Assignee: Rui Fan
>            Priority: Minor
>              Labels: pull-request-available, starter
>
> Some modules added the {{TestLoggerExtension}} to the 
> {{org.junit.jupiter.api.extension.Extension}} resource file. All test classes 
> of these modules don't need add the 
> {{@ExtendWith(TestLoggerExtension.class)}}  at class level.
> This JIRA propose clean up the {{@ExtendWith(TestLoggerExtension.class)}}  
> for modules that added the {{TestLoggerExtension}} to the 
> {{org.junit.jupiter.api.extension.Extension}} resource file.
> Update: We could also investigate in what extend we could remove the 
> {{org.junit.jupiter.api.extension.Extension}} resource files from certain 
> modules. It only has to be present once on the classpath. A single location 
> for this configuration would be nice (e.g. putting it in 
> {{flink-test-utils-parent/flink-test-utils-junit}}). But I think not all 
> modules have this one as there dependency. So, having a single resource file 
> for configuring this might be not possible. But at least, we can reduce the 
> number of files to a minimum.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to