Skip to content

Limit code coverage assessment to within a given directory for efficiency #41626

@IanButterworth

Description

@IanButterworth

Code coverage has --code-coverage=user but for CI most of the time you only care about coverage within the repo being tested.

Code coverage also slows execution down a fair bit.

Would it be possible to add the option to --code-coverage=/path/to/repo in such a way that would make it more efficient?

One thought was if the source file info was within the linetable? That could make it relatively simple to extend functionality to do_coverage, perhaps?

auto do_coverage = [&] (bool in_user_code) {

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureIndicates new feature / enhancement requests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions