Skip to content

Reduction in total unit test coverage is too stringent and drives unwanted behaviour #67

Open
@ben-sagar

Description

@ben-sagar

In the section on unit test coverage in the common coding standards it says:

All changes must have sufficient coverage and the overall total coverage must not decrease.

The use of the phrase "must not decrease" causes the following effects:

  • individual PRs fail review even if, for example, the total coverage has only dropped from 95.6% down to 95.4%, i.e. by a very small amount and still comfortably above the 90% standard
  • total coverage levels continuously creep up as it is not considered acceptable to ever lower it, so it only ever gets higher

It would be better if this could say something like:

All new or changed code must have sufficient coverage and the overall total coverage must not decrease below 90%.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions