ordinals/ord

Track test coverage on CI

Open

#1,568 opened on Feb 7, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (1,479 forks)github user discovery
good first issue

Repository metrics

Stars
 (3,955 stars)
PR merge metrics
 (Avg merge 15d 21h) (5 merged PRs in 30d)

Description

Would be great to track test coverage on CI. This would make a great first issue for someone who knows about GitHub CI and Rust test coverage!

  • Add a separate CI job
  • Figure out how to see test coverage results

I don't want a bot spamming PRs with comments about test coverage reports.

Contributor guide

Research direction
Research how to add a CI job for Rust test coverage. Look into tools like tarpaulin or grcov. Set up a GitHub Actions workflow that runs tests with coverage and outputs the result without using a commenting bot.
Tech stack
rust
Domain
ci cddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRustGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80