-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suddenly stopped working #448
Comments
@robross0606 Thanks for the ticket! |
I just realized that the coverage indicator on the bottom bar is showing the coverage of each opened file instead of the overall test coverage. Did it always do this? It seems strange to show "No Coverage" when no files are opened instead of showing the project's overall coverage. Why not show this when no file is open? |
I also noticed that the coverage numbers in the bottom are are truncating decimals instead of rounding. For example, one of my files has 96.77% coverage but coverage gutters reports 96% coverage instead of 97%. |
@robross0606 Interesting! I would have to rack my brain but I think the bottom coverage indicator always showed the current files covered lines. There definitely could be improvements here for the rounding, total project coverage, etc but finding dev time for improvements / open source contributions is the usual bottleneck.
Some more debugging we can do, try to check out the example project in this repo and see if the coverage is showing up correctly there. If it is, then maybe there are some settings within your other project that is preventing the visualization. |
Describe the bug
This has been working fine for at least a year if not longer. Suddenly all my projects insist there is "No Coverage" even though my user config is set to
analysis/**/index.html
and the following file tree exists in the project:And the HTML contents look normal:
Expected behaviour
Coverage would continue to be detected as it has for the last year.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: