Skip to content

Stripping spec coverage should be a configurable option #53

Open
@bahmutov

Description

@bahmutov
Contributor

As asked in #52 the user wants to have spec file coverage in the report. Right now we strip this information, leaving code coverage for application source code only (see https://github.com/cypress-io/code-coverage/blob/master/support.js#L63). Make it into a configurable option.

Activity

cmelion

cmelion commented on May 30, 2022

@cmelion

It would be very useful to get coverage reports for step files. IDE integrations make it very easy to determine when step implementations for [Given, When, Then and End] are missing but the converse isn't true and for larger projects it's possible end end up with deprecated or duplicate step implementations.

For Example

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

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @cmelion@bahmutov

        Issue actions

          Stripping spec coverage should be a configurable option · Issue #53 · cypress-io/code-coverage