ctest: allow testing individual modules
Open
Nobody has claimed this yet.
ctest
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 69
Description
#5326 surfaced a usecase for testing a single module in ctest. The goal
here would be to change the entry point to the ctest::generate_test
function to allow taking an optional module path, beyond the filesystem
path we currently pass to the crate root.
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
Start by locating the ctest::generate_test entry point and tracing how the current filesystem path is passed to the crate root. Check how module paths are represented and how existing ctest invocations are tested. Done means the entry point accepts an optional module path while preserving crate-root testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100