Skip to content
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.

Sign up for GitHub

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

Jump to bottom

no coverage of log statement (using grizzled) #137

Open
rombautt opened this issue Sep 30, 2015 · 2 comments
Open

no coverage of log statement (using grizzled) #137

rombautt opened this issue Sep 30, 2015 · 2 comments
Assignees
@sksamuel
Labels
coverage-gap

Comments

@rombautt
Copy link

scoverage
@sksamuel sksamuel self-assigned this Jun 2, 2016
@mirkof
Copy link

mirkof commented Jan 20, 2017 •
edited
Loading

I'm getting the same problem, but with Play. Looks like this only happens with interpolated strings.
It downgraded the coverage most of files from 3% to 20%.
Any plans to fix this?

@andreisilviudragnea
Copy link

andreisilviudragnea commented Feb 14, 2022 •
edited
Loading

@mirkof #426 is related to this. Scoverage does not support interpolated strings for now.

@andreisilviudragnea andreisilviudragnea mentioned this issue Feb 14, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sksamuel sksamuel

Labels
coverage-gap
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rombautt @sksamuel @mirkof @andreisilviudragnea