test cases coverge `coverage.Icov` is empty
See original GitHub issueI tried cloning and running test coverage but coverge.Icov
is empty.
Steps to reproduce:
-
clone and
npm install
-
npm run test:cov
All test cases succeed but coverage looks like this in the terminal
----------|----------|----------|----------|----------|----------------|
File | % Stmts | % Branch | % Funcs | % Lines |Uncovered Lines |
----------|----------|----------|----------|----------|----------------|
All files | Unknown | Unknown | Unknown | Unknown | |
----------|----------|----------|----------|----------|----------------|
and the coverage.Icov
file is empty
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
flutter test --coverage generate empty lcov.info #71467 - GitHub
passed first triage tests are present, the PR follows the PR template, no obvious coding errors severe: regression. tool.
Read more >Karma coverage always coming empty - Stack Overflow
Explanation: coverage tests your code against your unit tests - you need to supply entry point for ... In my case, the original...
Read more >Command line usage — Coverage.py 6.4.4 documentation
lcov – Produce an LCOV report with coverage results. ... In these cases, you can collect coverage data for each test run, and...
Read more >Code coverage testing - Visual Studio (Windows)
Learn how to use the code coverage feature of Visual Studio to determine what proportion of your project code is being tested by...
Read more >1.3. Branch Coverage
Only difference occurs when branches are "empty": ... In these cases branch coverage would require tests in which x and z are positive....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Absolutely. It’s a race to the PR! 😄
This days I’ve been working on the issue and for now I am stuck and perhaps need some help or advise. For now I have managed to change config of the nyc (istanbul cli) as shown on the picture below:
and all the src folder files appear to be in the report but with some kind of strange coverage results
![screen shot 2017-12-12 at 11 21 36 am](https://user-images.githubusercontent.com/14336732/33874189-ebb72b12-df2e-11e7-83d2-469f11aecbbb.png)
Current investigaton and nyc/babel/istanbul issues checking didn’t point at the idea of what could have happened here. Any ideas from anyone where to point the attention to? Original changes can be found in the fork