Skip to content

deno test --coverage Strategy Documentation #1412

@andy-preston

Description

@andy-preston

I'd really like to see a couple of lines in the test --coverage documentation.

There's an issue that code coverage is given by many test runners as a simple percentage.
But the question we have to ask is "a percentage of what, exactly?"

  • This could be simply the number of lines that have been covered.
  • Or, we should expect, that whitespace and empty statements are ignored.
  • Or, you can create a control-flow graph and provide a percentage of nodes of this graph that are covered.
  • Etc, etc, etc.

It's always an option to look at the source code and determine the strategy used by deno test but it would be nice if there was a short statement in the documentation that informed the casual reader just so that we know what the percentage given is a percentage of.

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