Skip to content

[WIP] Add code coverage grading workflow#13140

Draft
Pearl1594 wants to merge 1 commit intomainfrom
code-cov-grade
Draft

[WIP] Add code coverage grading workflow#13140
Pearl1594 wants to merge 1 commit intomainfrom
code-cov-grade

Conversation

@Pearl1594
Copy link
Copy Markdown
Contributor

Description

This PR adds a github workflow to add grades to the code coverage. An attempt to encourage increasing overall test coverage of the project.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@codecov
Copy link
Copy Markdown

codecov Bot commented May 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 18.08%. Comparing base (72b99a3) to head (971813d).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #13140      +/-   ##
============================================
- Coverage     18.08%   18.08%   -0.01%     
- Complexity    16718    16750      +32     
============================================
  Files          6037     6037              
  Lines        542546   543894    +1348     
  Branches      66432    66922     +490     
============================================
+ Hits          98146    98378     +232     
- Misses       433378   434483    +1105     
- Partials      11022    11033      +11     
Flag Coverage Δ
uitests 3.51% <ø> (ø)
unittests 19.24% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 22.71%
Branch coverage 17.13%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent
🟡 B 60–79% Good
🟠 C 40–59% Acceptable
🔴 D 20–39% Marginal — meets minimum gate
⛔ F < 20% Failing — below minimum gate

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 22.70%
Branch coverage 17.14%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent - this code sleeps well at night 😴
🟡 B 60-79% Good - almost there, don't stop now 😉
🟠 C 40-59% Acceptable - your code is wearing a seatbelt, but no airbags 😬
🔴 D 20-39% Marginal - boldly shipping where no test has gone before 🖖
⛔ F < 20% Failing - tests? what tests? 🔥

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 8, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant