Write tests, add coverage report to the CI
Open
Nobody has claimed this yet.
package:comms
package:flutter_comms
- Dominant language
- Dart
- Stars
- 22
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Ideally, most of the public API surface should be unit-tested.
Having code coverage report in the CI would also be great (so that after every PR we'd see whether the coverage increased or decreased).
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 by mapping the public API and inspecting the repository's existing CI setup. Clarify which API areas require unit tests and how coverage should be reported for each PR. Done means the agreed API surface is tested and CI publishes a coverage result for pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100