Early tests of JaCoCo 0.8.3 for me look better but still not great. The biggest problem is that JaCoCo is complaining that generated code (from kotlinx serialization) is not covered. I’m guessing that that is ok but I also could argue that it is part of the serialization library and should not be covered. Hmmm. Opinions?
02/01/2019, 3:07 PM
We've got jacoco configured on our end to ignore generated classes (by package -- we put all generated classes into a specific subpackage and ignore
). WIth 0.8.3 we're seeing much better coverage results, with the coverage of inline functions being the main thing that's missing.