Improve test coverage of `onefetch`
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- Rust
- Stars
- 12k
- Forks
- 332
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 17
Description
We're lacking both integration and unit tests to make sure we won't run into regressions after new development/refactoring.
Modules that should be covered by unit tests:
UI
Image backends
Info
Repo info fields
- repo/mod.rs
- author.rs
- commit.rs
- contributors.rs
- created.rs
- head.rs
- last_change.rs
- license.rs
- loc.rs
- pending.rs
- project.rs
- size.rs
- url.rs
- version.rs
Dependencies (package manager)
Language
Modules that should be covered by integration tests:
- info/mod.rs
- printer.rs (pointers --> https://github.com/o2sh/onefetch/pull/699#issuecomment-1179406932)
- git.rs (pointers --> https://github.com/o2sh/onefetch/pull/705#issuecomment-1193484501)
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 reviewing the unchecked modules: src/ui/printer.rs, the image backends, src/info/repo/loc.rs, pending.rs, version.rs, and the integration targets src/ui/printer.rs and src/info/git.rs. Read the pointers in pull requests 699 and 705, then inspect existing tests. Done means adding the requested unit and integration coverage for the remaining modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- cli, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100