You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+8-1
Original file line number
Diff line number
Diff line change
@@ -549,14 +549,21 @@ Deeply nested objects will sometimes have `[object Object]` values printed. You
549
549
DEBUG_DEPTH=10 DEBUG=code-coverage npm run dev
550
550
```
551
551
552
-
###Common issues
552
+
## Common issues
553
553
554
554
Common issue: [not instrumenting your application when running Cypress](#instrument-your-application).
555
555
556
556
If the plugin worked before in version X but stopped after upgrading to version Y, please try the [released versions](https://github.com/cypress-io/code-coverage/releases) between X and Y to see where the breaking change was.
557
557
558
558
If you decide to open an issue in this repository, please fill in all information the [issue template](https://github.com/cypress-io/code-coverage/blob/master/.github/ISSUE_TEMPLATE/bug_report.md) asks for. The issues most likely to be resolved have debug logs, screenshots, and hopefully public repository links so we can try running the tests ourselves.
559
559
560
+
### Coverage reporting timeouts
561
+
562
+
If the plugin times out when sending coverage report data to be merged, this may be due to a very large
563
+
report being sent across processes. You can batch the report by setting the `sendCoverageBatchSize` environment
564
+
variable in your `cypress.config.js` file's 'env' section. Assign the variable an integer value representing
565
+
the number of report keys to send per batch.
566
+
560
567
## Contributing
561
568
562
569
You can test changes locally by running tests and confirming that the code coverage has been calculated and saved.
0 commit comments