cypress-io / cypress-io/code-coverage
NYC instrumentation report contains instrumented files
- Dominant language
- TypeScript
- Stars
- 445
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
**Logs and screenshots**

**Versions**
- What is this plugin's version? If this is NOT the latest [released version](https://github.com/cypress-io/code-coverage/releases), 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](https://github.com/cypress-io/code-coverage#instrument-your-application), 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](https://github.com/istanbuljs/nyc#configuration-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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.