ci: improve test coverage
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hmm... I considered that test CI for individual utils are dupe of full test, but we need
cargo check --tests --no-default-features --features uu_* on CI at least for.
Originally posted by @oech3 in https://github.com/uutils/coreutils/issues/11792#issuecomment-4236637307
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
No CI file or test entry point is named. Start by locating the repository's CI workflow and existing test jobs, then determine where feature-specific checks belong. Done means CI runs cargo check --tests --no-default-features --features uu_* for the required utilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100