Currently, the repository uses pytest for unit testing, but there is limited visibility into how code coverage is being measured and reported. There is no clear configuration or documentation indicating:
- Whether coverage is being tracked using pytest-cov or another tool
- What the current coverage percentage is
- Which modules/files are included or excluded from coverage
- How coverage reports are generated and consumed (CLI, HTML, CI pipeline, etc.)
This makes it difficult to evaluate test completeness and identify untested parts of the codebase.
Currently, the repository uses pytest for unit testing, but there is limited visibility into how code coverage is being measured and reported. There is no clear configuration or documentation indicating:
This makes it difficult to evaluate test completeness and identify untested parts of the codebase.