Setup Integration Testing
Open
- Dominant language
- Erlang
- Stars
- 15
- Forks
- 2
- Avg merge
- 9h 58m
- Merged PRs (30d)
- 2
Description
Integration testing is required to verify correctness. Enabling integration tests involves closing the attached sub-issues. See also:
- https://arrow.apache.org/docs/format/Integration.html#example-ipc-format
- https://arrow.apache.org/docs/developers/continuous_integration/archery.html
Contributor guide
Research direction
Start by reviewing the attached sub-issues, then read the Apache Arrow Integration example IPC format documentation and the Archery continuous-integration documentation linked in the issue. Done means the required sub-issues are addressed and integration tests are enabled and verifying correctness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100