Improve test coverage
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
The issue names no files, tests, or entry points, so first inspect the existing unit-test layout and identify the large untested parts of the Python codebase. Done means adding meaningful unit tests that substantially improve coverage, but the issue does not define a target percentage or specific scope.
Written by the indexing model from the issue text.
Description
At the moment the unit test coverage is about 48%, and large parts of the code are untested.
- Dominant language
- Python
- Stars
- 12
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
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 BlueBrain/morphoclass
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
BlueBrain/morphoclass#87 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
BlueBrain/morphoclass#86 ·
-
bug
BlueBrain/morphoclass#79 · 2 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
BlueBrain/morphoclass#56 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
BlueBrain/morphoclass#48 ·
All issues in BlueBrain/morphoclass
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100