next-hat/nanocl

Tests: Improve coverage.

Open

#331 opened on May 28, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (51 forks)auto 404
cliclientdaemonenhancementgood first issuehelp wantedncdnsncproxyndnsnproxystubstestsutils

Repository metrics

Stars
 (983 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. It could be nice to try to improve the code coverage as much as possible. Arround 75% would be really nice ! You should be able to go on this website to see what is covered or not !

I'll keep this issue open till the goal of 75% is reached.

Contributor guide

Research direction
Use codecov.io to identify uncovered code in the repository. Write new test cases in Rust using the existing test framework, and run `cargo test` to ensure they pass. Focus on areas with low coverage.
Tech stack
rust
Domain
backendinfrastructure
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
GitRustBasic testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80