PYBIND11_TEST_OVERRIDE -> PYBIND11_SELECTED_TESTS
Open
Nobody has claimed this yet.
build system
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
-DPYBIND11_TEST_OVERRIDE easily gets me on the wrong track ("are we testing overrides?").
Maybe PYBIND11_SELECTED_TESTS?
Originally posted by @rwgk in https://github.com/pybind/pybind11/pull/2377
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for PYBIND11_TEST_OVERRIDE and inspect every use of the test-selection macro. Rename the references consistently to PYBIND11_SELECTED_TESTS, then run the relevant test or build checks to confirm selected tests still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100