richardforrestbarker
commented
2 years ago I think this is the best place for my report on a similar Issue.
Steps to reproduce JaCoCo version: 0.8.7 Operating system: Mac OS Tool integration: Gradle, IntelliJ Complete executable reproducer:
Steps: Using a project correctly configured with JaCoCo, with several packages and classes. Clean and Build the project Check that all expected packages are included in JaCoCo's report. On a single class, create / use an annontation meeting the requirements to trigger JaCoCo to ignore it for code coverage, in any package exoected to exist in the report. Clean and Build the project. Check that the expected packages are included in JaCoCo's report and note that the package containing the annontated class and all of its classes are missing.
Expected behaviour Given an annotation with the word Generated in it's name on a given class in a given package, when JaCoCo generates reports, then only the class annontated as such must be ignored for the purposes of the report, and nothing else.
Actual behaviour Entire package is filtered from code coverage, not just the class.
Basically class A and class B are in package X; class C is in package X.Y; and class D is in package Z. When class A is annontated with a runtime or class retained annotation containing Generated in it's name (like lombok's lombok.Generated which is retained at runtime) then all classes in package X are ignored. Packages X.Y and Z are not ignored in this case which is expected.
Godin
0d00
marchof
XenoAmess
knutwannheden
THIS IS A BUG TRACKER ONLY. FOR QUESTIONS PLEASE CHECK FAQ OR USE FORUM:
http://www.jacoco.org/jacoco/trunk/doc/faq.html
https://groups.google.com/forum/?fromgroups=#!forum/jacoco
Please understand that ISSUES WITHOUT FOLLOWING INFORMATION WILL BE CLOSED WITHOUT COMMENTS! Thank you for filling bug report!
Steps to reproduce
Expected behaviour
Just because an annotation has "Generated" in the name doesn't mean that it should be filtered from code coverage. The documentation that I could find for this filter feature of JaCoCo specified that the annotation name itself should only be named "Generated", which makes sense.
To make the filter even more explicit, and meaningful, maybe an annotation name like "JaCoCoIgnore" should be used. Also, JaCoCo could provide the filter annotations in a separate library.
Actual behaviour
Any annotation that has "Generated" in the name is filtered and not included in the code coverage.
(In case of exceptions provide FULL STACKTRACE)
// class without TestGeneratedTheory annotation public class TestThisCodeCoverage {
public void testThisMethod() { System.out.println("in testThisMethod"); }
}
// test class to test TestThisCodeCoverage public class TestThisCodeCoverageTest {
@Test public void testThisMethodTest() { new TestThisCodeCoverage().testThisMethod(); }
}
// annotation class to test the "Generated" theory of filtering when an annotation has "Generated" in the name @Retention(RUNTIME) @Target(TYPE) public @interface TestGeneratedTheory {
}
// class with TestGeneratedTheory annotation // because this annotation has "Generated" in the name, JaCoCo will filter this class in code coverage @TestGeneratedTheory public class TestThisCodeCoverage {
public void testThisMethod() { System.out.println("in testThisMethod"); }
}