-
Consider using Istanbul
-
Add ability to generate full code coverage reports. Requested by several users.
-
I'm not sure why coveralls is report 0% coverage. It might have to do with using `@babel/register`. I was thinking we might look at moving to `jest` which also produces coverage reports doesn't requ…
-
### Describe the bug
I have a UI component that has no functions in it but `vitest run --coverage` reports 0% coverage for functions.
If there are no functions to test, the coverage reporter shoul…
-
One scenario I have is a program written in rust that exposes the http interface and does not generate Python-related dependency packages via pyo3.
Invoke http interface directly by executing request…
-
Collating coverage for TypeScript takes some 35 seconds on my machine. I know it's a lot of data so I'm not expecting instant, but I was curious and ran https://www.npmjs.com/package/pprof-it on `c8 r…
-
Code coverage reports from the VM are based on invocation counters on functions (Function) and call sites (ICData). If the invocation counter is non-zero, the position is a hit, otherwise a miss. When…
-
I'm currently trying to run this GH Action as part of a longer action that generates coverage and sends to Codacy. The relevant Codacy part of the YAML is:
```
- name: Generate Coverage
…
-
We need to generate code coverage reports. We can use Clang source-based coverage: https://clang.llvm.org/docs/SourceBasedCodeCoverage.html
This will be a new build type (or multiple new build type…
-
## Link to bug demonstration repository https://github.com/meanstackmax/demo-test-coverage/tree/main
## Expected Behavior
Vitest and storybook should use the same source map outputted, thus the …