Skip to content

Set up code coverage reports #208

@chandryan

Description

@chandryan

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions