When running the test suite of MySQL2 with c8 using --all combined with --include, some files that exist and match the include patterns become invisible in the coverage report when totally uncovered.
For context, here is the coverage configuration used:
{
"all": true,
"include": ["index.js", "promise.js", "lib/**/*.js"],
"exclude": ["mysqldata/**", "node_modules/**", "test/**"],
"reporter": ["text", "lcov", "cobertura"],
"statements": 80,
"branches": 80,
"functions": 77,
"lines": 80,
"checkCoverage": true,
"clean": true
}However, lib/results_stream.js and lib/packets/binlog_query_statusvars.js don't appear in the report.
Expected behavior:
When bypassing c8's filtering (e.g., collecting V8 coverage data directly and calling Report programmatically) from my custom plugin that uses C8 behind the scenes, both files correctly appear with 0% coverage, confirming they exist and match the patterns.
When running the test suite of MySQL2 with c8 using
--allcombined with--include, some files that exist and match the include patterns become invisible in the coverage report when totally uncovered.For context, here is the coverage configuration used:
{ "all": true, "include": ["index.js", "promise.js", "lib/**/*.js"], "exclude": ["mysqldata/**", "node_modules/**", "test/**"], "reporter": ["text", "lcov", "cobertura"], "statements": 80, "branches": 80, "functions": 77, "lines": 80, "checkCoverage": true, "clean": true }However,
lib/results_stream.jsandlib/packets/binlog_query_statusvars.jsdon't appear in the report.Expected behavior:
When bypassing c8's filtering (e.g., collecting V8 coverage data directly and calling
Reportprogrammatically) from my custom plugin that uses C8 behind the scenes, both files correctly appear with 0% coverage, confirming they exist and match the patterns.Note