oasisprotocol / oasisprotocol/oasis-core
Improve test coverage
Open
Nobody has claimed this yet.
c:testing
epic
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
As of the beginning of Q3 2019, code coverage is ~54% for Go and ~16% for Rust.
Goals
- Go test coverage > X%
- Rust code coverage > Y%
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
Start by reviewing the linked Go coverage issue (#1134) and Rust coverage issue (#968), since this issue does not name files, tests, or target values. Determine the agreed X% and Y% goals and the relevant coverage commands or test areas there; done means both language-specific coverage targets are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rust
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100