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

Jacoco reports coverage for empty private constructors #298

Closed
veita opened this issue Mar 18, 2015 · 1 comment
Closed

Jacoco reports coverage for empty private constructors #298

veita opened this issue Mar 18, 2015 · 1 comment
Assignees
@marchof
Labels
declined: duplicate ❌ This issue or pull request already exists

Comments

@veita
Copy link

veita commented Mar 18, 2015

However, empty private constructors are quite common to prevent classes from being instantiated.

As a result in such cases Jacoco reports code coverage worse than it actually is.

It would be nice to have a mechanism to handle this case, e.g. with an annotation or whitelist.
@marchof
Copy link
Member

marchof commented Mar 19, 2015

Such a feature would be part of the filtering story #15. The case is on the list:

https://github.com/jacoco/jacoco/wiki/FilteringOptions

@marchof marchof closed this as completed Mar 19, 2015
@marchof marchof added the declined: duplicate ❌ This issue or pull request already exists label Mar 19, 2015
@Godin Godin mentioned this issue Feb 19, 2016
Closed
@jacoco jacoco locked and limited conversation to collaborators Jan 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@marchof marchof

Labels
declined: duplicate ❌ This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@veita @marchof