Skip to content

NYC instrumentation report contains instrumented files #861

Open
@1dukky

Description

@1dukky

Logs and screenshots
image

Versions

  • What is this plugin's version? If this is NOT the latest released version, can you try the latest version, please? 17

  • What is the Cypress version?

  • What is your operating system? macOS

  • What is the shell?

  • What is the Node version? 16.16

  • What is the NPM version? 8.11

  • How do you instrument your application? Cypress does not instrument web application code, so you must do it yourself.
    Application has been instrumented via nyc instrument --in-place command, then built and served via http-server

  • When running tests, if you open the web application in a regular browser and open DevTools, do you see window.__coverage__ object? Can you paste a screenshot?

Yes, window.coverage object is visible and reporter contains files.

  • Is there a .nyc_output folder? Is there a .nyc_output/out.json file? Is it empty? Can you paste at least part of it so we can see the keys and file paths?

yes, out.json as well as report is visible and contains data. Part of it visible on screenshot above.

  • Do you have any custom NYC settings in package.json (nyc object) or in other NYC config files?
  • Do you run Cypress tests in a Docker container?
    no
    Describe the bug
    After running tests, nyc instrumentation report contains files that are still instrumented, not "reverting" them back to raw state.

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