Skip to content

ci: include gtests in code coverage report#3385

Open
harrylin98 wants to merge 1 commit intovalkey-io:unstablefrom
harrylin98:Fix_code_cov
Open

ci: include gtests in code coverage report#3385
harrylin98 wants to merge 1 commit intovalkey-io:unstablefrom
harrylin98:Fix_code_cov

Conversation

@harrylin98
Copy link
Contributor

@harrylin98 harrylin98 commented Mar 19, 2026

The change includes running gtest unit tests in the code coverage report.

@harrylin98 harrylin98 force-pushed the Fix_code_cov branch 5 times, most recently from 2aa0f43 to ae881d3 Compare March 20, 2026 04:06
@codecov
Copy link

codecov bot commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.37%. Comparing base (543a6b8) to head (3f4a300).
⚠️ Report is 3 commits behind head on unstable.

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable    #3385      +/-   ##
============================================
+ Coverage     74.56%   76.37%   +1.81%     
============================================
  Files           130      159      +29     
  Lines         72730    79631    +6901     
============================================
+ Hits          54228    60815    +6587     
- Misses        18502    18816     +314     

see 72 files with indirect coverage changes

🚀 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.

@harrylin98 harrylin98 marked this pull request as ready for review March 20, 2026 15:03
@harrylin98 harrylin98 requested a review from madolson March 20, 2026 15:04
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
- name: Install gtest
run: |
git clone --depth 1 https://github.com/google/googletest.git

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same ask as on the other PR, should we pin to a major version here instead of just taking git?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right about this. I will pick a stable version.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants