cypress-io / cypress-io/code-coverage

`all:true` not working with Next application

Open
#552 10 comments 4 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
445
Forks
115
PR merge metrics
No merged PRs in 30d

Description

**Versions**

- What is this plugin's version? 3.9.12
- What is Cypress version? 8.2.0
- What is your operating system? Mac OS 12.1
- What is the shell? ZSH
- What is the Node version? 14.18.2
- What is the NPM version? 8.3.2
- 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 need to do it yourself.
Like mentioned in the installation guide here
- When running tests, if you open the web application in regular browser, and open DevTools, do you see `window.__coverage__` object? Can you paste a screenshot?

I don't think I do but I get coverage in the end.

- Is there `.nyc_output` folder? Is there `.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?

This is generated, but no empty objects for empty files.

- 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)

```json
"nyc": {
"all": true
}
```

- Do you run Cypress tests in a Docker container?
**No**

**Describe the bug**
I use the option `all:true` but I don't see all files. For example I have some files in `pages/..` which are not displayed at all. It seems that just loaded files are used.

The NYC options from the package.json are used because I fiddled around with the `include` parameter and it is filtering, so that seems to work. I don't see any difference in the output if I use `true` or `false` for the `all` option.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.