Frontends

Both GitHub and GitLab do provide features for displaying CI results through their web GUIs. Although they are not rich enough for displaying all the details, OSVR generators can provide stripped down file formats matching some of the supported readers; similarly to the JSON and xUnit outputs provided by VUnit.

Open Source Verification Report Explorer

It would be interesting to have a vendor agnostic tool for visualizing reports locally and/or in self-hosted services. Since XML, JSON or YAML are used, web technologies (HTML + CSS + JavaScript) feel like a sensible choice. Generating an static page which can be hosted on GitHub Pages or GitLab Pages allows granular analysis of CI results, while also being usable locally. There are several simple and not-so-simple solutions available for xUnit files:

Similar solutions exist based on unittest or pytest:

As a complement, extending pyucis-viewer might be evaluated, for providing a Qt based solution. pyucis-viewer currently provides a simple bar-chart viewer for coverage data read via pyucis.

GitHub

Although there is no official feature for using the GitHub Checks API, there are some community actions for e.g. analysing xUnit files: publish-unit-test-results. There are also multiple bindings in JavaScript, Python or golang for interacting with GitHub’s API.

GitLab

Apart from unit test reports, GitLab supports over a dozen artifact reports.

Grafana

On top of visualizing individual reports or sets of reports at one point in time, tracking the evolution of certain metrics throughout the development of a project can provide valuable insight. GitLab does have a built-in Prometheus monitoring system and Grafana can be optionally used as a dashboard: docs.gitlab.com: Grafana Dashboard Service. Therefore, it would be useful to send OSVR reports to either Prometheus or some other temporal database (say Graphite, InfluxDB, etc.).

References