ci: upload Hardhat-tests coverage to Codecov - #1388
Conversation
|
ef7e7d4 to
b8963bf
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1388 +/- ##
==========================================
+ Coverage 74.41% 79.27% +4.85%
==========================================
Files 444 444
Lines 76051 76051
Branches 76051 76051
==========================================
+ Hits 56597 60293 +3696
+ Misses 17462 13630 -3832
- Partials 1992 2128 +136 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The hardhat-tests workflow already ran `cargo llvm-cov report` against the JS test run, but the resulting `codecov.json` was never uploaded. Hardhat-tests is the suite that exercises the napi binding code paths end-to-end (subscriptions, providers, Solidity test runs, stack-trace decoding), so dropping its report leaves those files looking under-covered on every PR. Add the Codecov upload step matching the pattern used in edr-ci.yml.
b8963bf to
adea231
Compare
popescuoctavian
left a comment
There was a problem hiding this comment.
Great find, thanks!
Why
The
hardhat-testsworkflow already runscargo llvm-cov reportafter the JS test run and produces acodecov.json, but it never had an upload step — the file was generated and discarded. That suite exercises the napi binding code paths end-to-end (subscriptions, provider lifecycles, Solidity test runs, stack-trace decoding), so without its upload those files look under-covered on every PR even though they are tested.Most visible on #1385 (napi v3 migration): patch coverage 52% with
call_override.rs,provider.rs, andtrace/debug.rsshowing 0% — exactly the files Hardhat-tests would cover.Change
Add a
codecov-actionupload step tohardhat-tests.ymlaftercargo llvm-cov report, matching the pattern already used by the three uploads inedr-ci.yml(matrix-named, SHA-pinned,fail_ci_if_error: false,CODECOV_TOKEN).