llama90 commented on issue #42002:
URL: https://github.com/apache/arrow/issues/42002#issuecomment-2151510108
Yes, I would. I have a plan to follow these steps:
1. Replace `org.junit` with `org.junit.jupiter.api`.
2. Update `no suitable method found for assertEquals (string, xxx, yyy)` to
`(xxx, yyy, string)` because in JUnit 5, the "message field" has changed.
3. Update `Assertions.assertXXX` to `assertXXX` using static imports.
- I believe using static imports will make the code base clearer.
4. Update annotations such as `@Before`, `@BeforeClass`, `@After`,
`@AfterClass`, etc., to their JUnit 5 equivalents.
5. ...
99. In the final step, replace `junit-vintage-engine` with
`junit-jupiter-engine` to prevent using JUnit 4 statements.
- Maybe, it should be changed after all JUnit 4 statements are removed.
Additionally, I will review documentation like [Migrating from JUnit 4 to
JUnit 5](https://www.baeldung.com/junit-5-migration).
Let me know if you have any suggestions or additional steps.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
