Vetrix Docs

Code coverage

When a pipeline produces a coverage report, its results appear on the pipeline's detail page as a Coverage report panel. The panel shows the overall percentage of statements covered for that run, a breakdown of the covered and total counts, and a link to the full report when the pipeline saved one. Coverage is recorded per pipeline run, so each run carries its own figures against the commit it built.

Where to find it

  • URL: open a single pipeline at gitvetrix.com/<owner>/<repo>/pipelines/<id>.
  • Navigation: open a repository, select Pipelines in the side navigation, and select View on the pipeline you want. The Coverage report panel sits near the top of the pipeline detail, above the list of jobs. Pipelines that produced no coverage show no panel at all.

Read the coverage totals

  1. Open the pipeline whose coverage you want to read.
  2. Find the Coverage report panel above the jobs list.
  3. Read the large figure under Total: it is the percentage of statements covered for the run, followed by the word statements. The percentage is coloured to signal how high it is — green when it is strong, amber in the middle range, and red when it is low — but the number itself is the reliable signal.
  4. Read the supporting figures beside it:
    • Covered — how many statements the run exercised.
    • Total — how many statements were measured in all.
    • Packages — how many packages the report grouped the results into.
    • Commit — the short identifier of the commit the coverage was measured against. When the run could not attribute the result to a commit, this reads unknown commit.
    • Generated — the time the report was produced, shown only when the run recorded it.

Open the full report

If the pipeline saved a full HTML coverage report, the panel header shows a View full HTML report link.

  1. Find the View full HTML report link in the top-right of the Coverage report panel.
  2. Select it to open the complete report, which breaks the results down file by file. When the pipeline did not save this report, the link is absent and only the totals are shown.

Tips

  • The coverage job ran but measured nothing. When a run completes its coverage step but has no statements to summarise, the panel shows a short message in place of the totals rather than a percentage. This is expected for a run that had nothing to measure.
  • Coverage is temporarily unavailable. If the panel cannot load the report because of a passing infrastructure problem, it shows a Coverage temporarily unavailable message with a Retry button. This does not mean the pipeline lacks coverage — select Retry after a moment to load it again.
  • A completed pipeline keeps its coverage. Because the figures are stored per run, older pipelines keep showing their coverage even after their build artifacts age out.
  • Security findings — the security scanning results for a repository, alongside coverage in the CI/CD area.