Skip to content

ci(coverage): remove || true test-masking#130

Merged
mastermanas805 merged 1 commit into
mainfrom
ci/remove-coverage-test-masking
May 21, 2026
Merged

ci(coverage): remove || true test-masking#130
mastermanas805 merged 1 commit into
mainfrom
ci/remove-coverage-test-masking

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Summary

  • Drop || true from the npm test -- --coverage step in .github/workflows/coverage.yml so the workflow conclusion reflects actual test status.
  • Move codecov upload to if: always() so coverage still uploads on test failure (data without the false-green).

Per audit at /tmp/ci-audit-2026-05-22.md and CLAUDE.md rule 12: shipped != verified.

Test plan

  • coverage workflow runs on this PR and reports actual test outcome
  • codecov upload still happens via if: always()

🤖 Generated with Claude Code

Per the audit at /tmp/ci-audit-2026-05-22.md, the coverage workflow's
test step was suppressing failures with `|| true` while still uploading
whatever partial coverage data accumulated. This made the workflow
report green even when tests failed silently — exactly the bug class
CLAUDE.md rule 12 calls out (shipped != verified).

Fix: drop `|| true`. Move codecov upload to `if: always()` so coverage
still uploads on test failures but the workflow conclusion now
reflects actual test status.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mastermanas805 mastermanas805 merged commit b9a30c8 into main May 21, 2026
10 of 11 checks passed
@mastermanas805 mastermanas805 deleted the ci/remove-coverage-test-masking branch May 21, 2026 19:13
@github-actions
Copy link
Copy Markdown

size-limit report 📦

Path Size
dist/assets/index-BwyF-Dau.js 143.87 KB (0%)
dist/assets/index-C9T0ot61.css 6.19 KB (0%)

mastermanas805 pushed a commit that referenced this pull request May 22, 2026
The `coverage` CI job runs `npm test -- --coverage` but the provider was
never declared in package.json, so the job has failed on every PR since
#130 un-masked it (MISSING DEPENDENCY @vitest/coverage-v8). Pin it to the
installed vitest version (1.6.1) so the coverage gate runs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mastermanas805 added a commit that referenced this pull request May 22, 2026
* test(coverage): drive A-M pages/components to >=95% line coverage

Adds vitest/@testing-library coverage for the first half (filenames A-M)
of src/pages and src/components: new tests for previously-untested pages
(Blog, Login, LoginCallback, Incidents, Checkout, Docs, ForAgents,
Contracts) and components (CustomDomainPanel, CodeBlock, CustomerDetailDrawer,
IssuePromoModal, Common pills/Sparkline/PromptCard), plus extended tests
for BillingPage (checkout error + verify-email gate + UpdatePaymentButton +
invoice period + formatAsOf), DeploymentsPage (status filter/bucket/sort/
no-match), and DeployDetailPage (stack-kind view chrome + tabs + Promote
upsell). Covers loading/error/empty/success states and user interactions.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* build: add missing @vitest/coverage-v8 devDependency

The `coverage` CI job runs `npm test -- --coverage` but the provider was
never declared in package.json, so the job has failed on every PR since
#130 un-masked it (MISSING DEPENDENCY @vitest/coverage-v8). Pin it to the
installed vitest version (1.6.1) so the coverage gate runs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* test(docs): make DocsPage TOC test resilient to empty docs corpus

The `coverage` CI job runs `vitest run` directly without the fetch-content
prebuild, so the .content/docs glob is empty and SECTIONS has zero entries.
Assert the TOC <ol> exists rather than requiring a populated section list.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude <claude@anthropic.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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