Commit 7f39d85
committed
Always run nyc report after CT tests so frontend coverage uploads on red CT runs
`test:coverage:ct` chained `playwright test ... && nyc report ...`, so a
failing CT run short-circuited before `nyc report` could turn the
per-test JSON files in .nyc_output into an lcov.info. The downstream
"Upload CT Coverage to Codecov" step (if: success() || failure()) then
errored with "No coverage reports found" and frontend-component did
not upload for that SHA.
Codecov's server-side aggregation of the merged `frontend` flag was
left with only frontend-unit (~23%) and frontend-e2e (~24%), pulling
the merged number down to ~33% even though the previous commit was
at ~67% — observed on six consecutive main commits 2026-04-26T01:02..
02:58Z (2d7033f..be5bcfc) before recovering on 3029839 once CT
started passing again.
Mirror the existing test:e2e:coverage pattern:
; CT_EXIT=$?; nyc report ... || echo "No coverage data to report"; exit $CT_EXIT
so nyc report runs regardless of test outcome and the lcov ships
even on red CT runs. frontend-component will still report a
slightly lower number when tests fail (failed tests register fewer
hits), but it will report — keeping the merged frontend flag's
denominator stable.1 parent 6bd7f26 commit 7f39d85
2 files changed
Lines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| 12 | + | |
12 | 13 | | |
13 | 14 | | |
14 | 15 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
100 | 100 | | |
101 | 101 | | |
102 | 102 | | |
103 | | - | |
| 103 | + | |
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
| |||
0 commit comments