[
https://issues.apache.org/jira/browse/HADOOP-19646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012279#comment-18012279
]
ASF GitHub Bot commented on HADOOP-19646:
-----------------------------------------
slfan1989 opened a new pull request, #7858:
URL: https://github.com/apache/hadoop/pull/7858
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
JIRA: HADOOP-19646. [JDK17] Migrate hadoop-aws module from JUnit4 Assume to
JUnit5 Assumptions.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Migrate hadoop-aws module from JUnit4 Assume to JUnit5 Assumptions
> ------------------------------------------------------------------
>
> Key: HADOOP-19646
> URL: https://issues.apache.org/jira/browse/HADOOP-19646
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: hadoop-aws
> Affects Versions: 3.5.0
> Reporter: Shilun Fan
> Assignee: Shilun Fan
> Priority: Major
>
> This task aims to migrate the test code in the {{hadoop-aws}} module from
> JUnit4's {{org.junit.Assume}} API to JUnit5's
> {{org.junit.jupiter.api.Assumptions}} API in order to unify the testing
> framework and improve maintainability.
> h4. Scope of changes:
> * Replace usages of {{{}Assume.assumeTrue(...){}}},
> {{{}Assume.assumeFalse(...){}}}, etc., with the corresponding methods from
> JUnit5, such as {{{}Assumptions.assumeTrue(...){}}};
> * Ensure the assertion logic remains consistent with the original behavior;
> * Update any outdated import statements referencing JUnit4's {{{}Assume{}}};
> * Verify that all affected unit tests pass correctly under JUnit5.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]