[Java] Improve testing of Dataset bindings
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
From https://github.com/apache/arrow/pull/13811
- We should ensure all types are tested
- We should organize tests in a way that Parquet, IPC, and eventually CSV/ORC can mostly share test code (save for perhaps skipping/overriding specific format-type pairs)
Incidentally: it may be good to incrementally port this module to JUnit5 and drop JUnit4
**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-17342) / @lidavidm
**Note**: *This issue was originally created as [ARROW-17342](https://issues.apache.org/jira/browse/ARROW-17342). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by locating the Java tests for Dataset bindings and reviewing how Parquet and IPC cases are currently organized. Check coverage for all types, then assess how the tests could share code across formats, including possible CSV and ORC cases; JUnit4-to-JUnit5 migration is noted as a secondary consideration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100