boostorg / boostorg/msm

Set up code coverage reports

Open
#208 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
40
Forks
59
PR merge metrics
No merged PRs in 30d

Description

Look into setting up code coverage reports to spot untested source code.

Cases such as a regression that was identified very late during the release activites (#205) can be more easily identified this way.

For the Boost CI these instructions are a helpful reference: https://github.com/boostorg/boost-ci/blob/master/docs/code-coverage.md

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.