vln-devsecops/Validate Coverage
Validate test coverage from XML files against minimum thresholds
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| coverage-file | Path to the coverage XML file (e.g., coverage/cobertura.xml) | yes | — |
| minimum-coverage | Minimum coverage percentage required (e.g., 85) | yes | 85 |
| coverage-type | Type of coverage XML format (clover, cobertura, jacoco) | no | cobertura |
| working-directory | Working directory where the coverage file is located | no | . |
| github-token | Token used to publish a commit status with the coverage result (e.g. ${{ github.token }}). Omit to skip status publishing entirely — the action behaves exactly as before. | no | — |
| status-context | Commit status context to publish under. Must start with "coverage" to be picked up by the org dashboard. | no | coverage/validate-coverage |
| json-report-file | Path to write a machine-readable JSON coverage report (relative to working-directory), for dashboards in other orgs that consume a workflow artifact instead of a commit status. Omit to skip report-file generation — the report-json output is still produced. | no | "" |
Outputs
| name | description |
|---|---|
| coverage-percentage | The actual coverage percentage found |
| status | Pass or fail status of the validation |
| report-json | A compact JSON string summarizing the coverage report (coverageFile, coverageType, coveragePercentage, minimumCoverage, status, covered, total, timestamp) |
| report-file | Path to the written JSON report file, relative to $GITHUB_WORKSPACE when the report lives under it (falls back to an absolute container path otherwise) so it can be used directly by later steps like actions/upload-artifact. Only set when json-report-file is provided and the write succeeds |