oppia / oppia/oppia-web-developer-docs
Document how to read backend coverage reports
Open
Nobody has claimed this yet.
bug
Impact: Medium
target: Q1 2025
Work: Low
- Dominant language
- Python
- Stars
- 18
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
- Document how to read backend coverage reports, specifically where "overall line coverage" is shown. See https://github.com/oppia/oppia/pull/17788#issuecomment-1503784737.
- Also suggest
python -m coverage htmlas an alternative way to read the coverage reports - Add a reference to https://github.com/oppia/oppia/wiki/Backend-tests#coverage-reports at the end of the CI log so that devs can discover this information.
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
Start with the linked PR comment and the Backend-tests coverage-reports wiki section, then locate the documentation page and CI-log entry point in the linked repositories. Done means the checklist is covered: explain where overall line coverage appears, mention python -m coverage html, and append the wiki link to the CI log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100