[repo-assist] ci: raise coverage thresholds to match current levels - #551
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
Coverage on the analyzer/factory source (excluding VS Code-API-dependent files not exercised by unit tests) has been at 98%+ for several runs while the c8 gate was still set at 80/80/88/95. Raise thresholds to 95/95/88/97 so future coverage regressions are caught by CI instead of drifting unnoticed, and exclude extension.js/configuration.js/providers/** (the same VS-Code-API surface excluded by PR #511) since they cannot be exercised in the headless unit test environment. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 This pull request was created by Repo Assist, an automated AI assistant.
Summary
The c8 coverage gate in
.c8rc.jsonwas left at 80% lines/statements, 88% branches, 95% functions, while actual coverage on the analyzer/factory source has been sitting at 98%+ for many runs. A gate this loose would let a real coverage regression slip through CI unnoticed until it had already grown large.What changed
out/extension.js,out/configuration.js, andout/providers/**from coverage, matching the same VS Code-API exclusion already used by PR [repo-assist] feat: add cognitive complexity diagnostics provider #511 (diagnostics provider) - these files depend on thevscodeAPI and cannot be exercised by the headlessmocha/c8unit test run; including them without a matching test harness would otherwise force thresholds back down to ~80%.Why
A meaningful coverage gate is one of the cheapest ways to prevent silent regressions. No production code changes.
Trade-offs
providers/**logic that can be unit-tested (pure helper functions, etc.), consider moving that logic out of the excluded files rather than adding it to a file this config skips.Test Status
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
releaseassets.githubusercontent.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Add this agentic workflow to your repo
To install this agentic workflow, run