Get test coverage to 100%
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the current test layout and coverage reports in the datatug and datatug-core repositories linked in the issue. The scope is not narrowed to files or tests; completion would require reaching 100% test coverage in the relevant repository or repositories.
Written by the indexing model from the issue text.
Description
We'd be welcome PRs that increase test coverage of https://github.com/datatug/datatug or https://github.com/datatug/datatug-core repositories.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 84
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.
More from datatug/datatug-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
datatug/datatug-cli#263 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
datatug/datatug-cli#261 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
datatug/datatug-cli#256 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
datatug/datatug-cli#262 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
datatug/datatug-cli#260 ·
All issues in datatug/datatug-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·