openedx / openedx/docs.openedx.org
Write Dev Guide > Code Coverage section
Open
Nobody has claimed this yet.
developers
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
- Author an article on how we use code coverage https://docs.openedx.org/en/latest/developers/references/legacy_guide/testing/code-coverage.html - addressed by https://github.com/openedx/docs.openedx.org/pull/432
- Move to "Writing Good Code" section (currently section 7)
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.
Research direction
Open the linked code-coverage article and the Dev Guide’s “Writing Good Code” section, currently section 7. Move the code coverage material into that section, then verify the documentation builds and the section appears in the intended location.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100