-
Notifications
You must be signed in to change notification settings - Fork 157
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
Why statement coverage is not 100% in this class? #382
Comments
Is it possible that your tests run without enabling debug logging? If you don't enable debug logging, then the message won't be evaluated because it is not needed. |
Ahhh yes this might be it. Do you have any idea what is the issue with the first image? |
So on the page in the first image if you click "Statement List", does it show you the statements that aren't covered? I'm assuming there are 3 looking at the numbers? |
🤔 really? That's odd as the first image you showed says there are 35 statements |
Yep I know! This is really word. Let me try reproduce it in a clean project I can share publicly... |
Also, for some reason the table is incomplete - it does not have the tests or code columns... |
I have another example to add to the "Why statement coverage not 100%" Code:
Test cases (scalatest):
Test Coverage: |
Hello!
I have a lot of small classes, where scoverage says the coverage is not complete - in this case:
And I can't figure out why... Is this a bug? Here is the example class (I've redacted the actual code):
Is this a bug? Or am I missing something?
I am using the latest version:
The text was updated successfully, but these errors were encountered: