Skip to content

Add coverage configuration #28

Description

@chillenzer

I would consider configuration for coverage beneficial (at least to know about it). My standard approach (in projects from scratch or when it is a manageable effort) is to aim for 100% coverage and explicitly and consciously exclude parts that do not need testing, e.g., the small main function. That is, I believe, a much healthier approach to code coverage than just monitoring its slow decay or trying to hit a target threshold but in that pursuit only covering unimportant lines.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions