← All finding types

new_code_coverage_below_minimum

New Code Coverage Below Minimum — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.

How to fix

Add tests that execute the lines this change added or modified medium effort

// The gate counts only the lines the change touched that the JaCoCo report instruments.
// Cover the new branches and error paths, then re-run the tests before the scan:
//   mvn test jacoco:report   (or: ./gradlew test jacocoTestReport)

What is measured

The lines a change adds or modifies (since its merge-base with the base branch) that the configured JaCoCo report instruments. Set coverage.newCodeMinimum in .driftrc.yml; without it the new-code coverage is reported and nothing is gated. A change that cannot be measured (no merge-base, a diff that cannot be read) is treated as not meeting the minimum. A changed source file the report does not cover at all is counted and shown, not treated as covered or uncovered.

Failing the build: the finding is major; set the Action's fail-on-severity: major (or a server gate on new major findings) to block a merge on it.

Trust boundary: the report is an output of your build, which runs the change's own code. Produce it in a workflow the change cannot alter, and keep the JaCoCo plugin configuration under code-owner review; PullGuard refuses a report committed to the repository and a report path changed by the change, but it cannot tell a genuine build output from one the build was changed to write.

Triage

This finding judges the change itself, so .pullguardignore, a committed baseline, delta mode and the scan cache do not remove it, and a pull request cannot lower or remove coverage.newCodeMinimum in its own configuration. To pass it, cover the changed lines — or change the minimum on the base branch through a reviewed change.