LEAP-Systems / LEAP-Systems/tesseract
Refactor Unittests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Once again a ton of changes are ongoing so I'm placing this on the back burner until we can get a stable version we are happy with. Coverage is going to complain, but for now it is safe to ignore.
These are the packages that require an expanded set of unittests:
- tcs
- wap
- file
- codec
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or test entry points are named. Begin by reviewing the existing unit tests and coverage for the tcs, wap, file, and codec packages, but wait until the project reaches the stable version referenced in the issue. Done means expanding coverage for those packages and confirming the resulting coverage concerns are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100