bazel-coverage-report-renderer: HTML Coverage Reports for Rules_Haskell

[ apache, build-tool, program ] [ Propose Tags ]

Generate coverage reports from Rules_Haskell Bazel coverage output

[Skip to Readme]
Versions [faq] 0.1.0
Dependencies base (>= && <4.13), cmdargs (>=0.10.20 && <0.11), directory (>= && <1.4), filepath (>= && <1.5), hxt (>= && <9.4), hxt-xpath (>= && <9.2), listsafe (>= && <0.2), MissingH (>= && <1.5) [details]
License Apache-2.0
Copyright 2019 Tweag I/O Limited
Author Tweag I/O Limited
Category Build Tool
Home page
Bug tracker
Source repo head: git clone
Uploaded by SebastianKazenbrootGuppy at Thu May 23 20:36:25 UTC 2019
Distributions NixOS:0.1.0
Executables bazel-coverage-report-renderer
Downloads 43 total (21 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs not available [build log]
Last success reported on 2019-05-23 [all 3 reports]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for bazel-coverage-report-renderer-0.1.0

[back to package description]


An executable which reads Bazel test.xml test results generated by bazel coverage for Rules_Haskell's haskell_test rule. These rules must have coverage_report_format set to "html" to be compatible with this tool.

Example Usage

If we have a target defined by the Rules_Haskell haskell_test rule, such as:

    name = "two-libs",
    srcs = [
    coverage_report_format = "html", # this must be set to "html" (not "text")
    expected_covered_expressions_percentage = ...,
    expected_uncovered_expression_count = ...,
    deps = [

If we run bazel coverage //path/to/package:two-libs, the HTML report files will be appended to the test log (visible with --test_output=all set, or by looking in the bazel-testlogs directory at the relevant test.xml file). Bazel test rules cannot generate output files, hence why we append the HTML reports directly into the testlog.

Next, to extract the HTML reports and make them viewable in a browser, we use this tool, the bazel-coverage-report-renderer. It's as simple as running:

bazel-coverage-report-renderer \
    --testlog=<path/to/bazel-testlogs>/<path/to/package>two-libs/test.xml \

The tool will tell you where you can find the resulting files. The hpc_index.html file is the homepage for your coverage results.