How are you guys dealing with code coverage? It s...
# composea
aoriani
08/10/2023, 4:24 PMHow are you guys dealing with code coverage? It seems that jacoco considers the code at bytecode which is more complex than the composable functions. Therefore it underreports coverage.
a
agrosner
08/10/2023, 8:41 PMIf you test the composables using paparazzi wouldn’t it count all of the code as covered?
Do you mean that because the lines of code grows with compose compiler it means lower % in a module than you expect?
a
aoriani
08/10/2023, 8:47 PMExactly. Sonar also uses jacoco data to calculate cyclomatic complexity. So it complains that my tests are not covering all conditionals. My composable has no conditionals at all. But if I decompiler I see that compose compiler has added several.
I found the related jacoco issue https://github.com/jacoco/jacoco/issues/1208
aoriani
08/10/2023, 8:49 PMhttps://www.jacoco.org/jacoco/trunk/doc/flow.html
mplementing a coverage tool that supports statement (C0) as well as branch coverage coverage (C1) requires detailed analysis of the internal control flow of Java methods. Due to the architecture of JaCoCo this analysis happens on the bytecode of compiled class files.
p
Peter Mandeljc
08/11/2023, 8:05 PMMaybe try Kover with IntelliJ engine?
a
aoriani
08/11/2023, 8:05 PMsomeone on my team tried , and not many improvements
2 Views