[Archery][Integration] Parameterize integration tests by language
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 88
Description
Currently, the matrix of which integration tests to run is done on a per test basis and is written in Python.
I propose that we lift this into a common configuration file (.yaml) that declares which tests each language supports, which is then harnessed during test execution to skip files that are not supported.
This allows for a better overview of which languages support what.
**Reporter**: [Jorge Leitão](https://issues.apache.org/jira/browse/ARROW-15668) / @jorgecarleitao
#### PRs and other links:
- [GitHub Pull Request #12409](https://github.com/apache/arrow/pull/12409)
**Note**: *This issue was originally created as [ARROW-15668](https://issues.apache.org/jira/browse/ARROW-15668). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by reviewing the Archery integration-test matrix currently written in Python and the linked pull request #12409. Define the shared YAML configuration for language support and verify that the test harness skips unsupported files while preserving the intended integration coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, yaml
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100