Increase code coverage
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by reviewing the existing test suite and API modules to find uncovered use cases, then add tests for the identified API paths and verify that coverage increases.
Written by the indexing model from the issue text.
Description
We'd like to have more tests to increase our code coverage. Also more tests around other use cases as well (other parts of the APIs).
- Dominant language
- Java
- Stars
- 136
- Forks
- 26
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 47
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 docling-project/docling-java
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
docling-project/docling-java#664 ·
-
docling-project/docling-java#598 · 9 comments · 1 reaction · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
docling-project/docling-java#557 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
docling-project/docling-java#184 · 5 comments ·
-
automation enhancement module:version-tester
docling-project/docling-java#134 · 2 comments · 1 assignee ·
All issues in docling-project/docling-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100