lsd-rs/lsd

Improve the code coverage

Open

#46 opened on Dec 9, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (434 forks)batch import
good first issuehelp wanted

Repository metrics

Stars
 (13,400 stars)
PR merge metrics
 (Avg merge 34d 3h) (2 merged PRs in 30d)

Description

For now the project is badly covered by the tests. It can be greatly improved.

Contributor guide

Research direction
Identify untested code modules by running coverage analysis tools like tarpaulin. Write unit tests for functions without tests, focusing on core logic.
Tech stack
rust
Domain
cli
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70