ctest: allow testing individual modules

Open
  • Is something wrong?
#5,457 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
testing-qa

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.

Description

ctest

#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.

Dominant language
Rust
Stars
2.6k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/libc

All issues in rust-lang/libc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.