uutils/coreutils

nohup: write unit tests to improve coverage

Open

#1,857 opened on Mar 21, 2021

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Rust (1,852 forks)batch import
U - nohupgood first issue

Repository metrics

Stars
 (23,246 stars)
PR merge metrics
 (Avg merge 9d 14h) (216 merged PRs in 30d)

Description

We almost don't have tests for nohup. We should have more: https://codecov.io/gh/uutils/coreutils/tree/master/src/uu/nohup/src

Should be added here: https://github.com/uutils/coreutils/blob/master/tests/by-util/test_nohup.rs

Contributor guide

Research direction
Review the existing test structure in tests/by util/test nohup.rs and add unit tests covering the nohup command's functionality. Use the codecov report (https://codecov.io/gh/uutils/coreutils/tree/master/src/uu/nohup/src) to identify untested code paths. Follow patterns from other test files in the by util directory to write idiomatic tests using the test framework.
Tech stack
rust
Domain
clitesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustbasic testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70