You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under certain circumstances - it seems related to @JvmOverloads functions with defaults, Kover produces line coverage information that are neither covered nor uncovered.
In this example, line 195, which only has a } is marked as green in the HTML interface, but if one looks at the XML file, there is something weird:
<linenr="195"mi="0"ci="0"mb="0"cb="0"/>
Basically, this line is neither covered nor uncovered. While the HTML report says its ok, there are other tools (such as codecov), which are completely thrown by thus and report it as uncovered.
Expected behavior
I would expect, that this line actually would not exist at all.
Reproducer
A commit where it definitely exists: csaf-sbom/kotlin-csaf@11844ec. We are trying to workaround this, so later commits on main might not be used for reproduction.
Reports
see above
Environment
Kover Gradle Plugin version: 0.8.3
Gradle version: 8.10
Kotlin project type: Kotlin/JVM
The text was updated successfully, but these errors were encountered:
Describe the bug
Under certain circumstances - it seems related to
@JvmOverloads
functions with defaults, Kover produces line coverage information that are neither covered nor uncovered.In this example, line 195, which only has a
}
is marked as green in the HTML interface, but if one looks at the XML file, there is something weird:Basically, this line is neither covered nor uncovered. While the HTML report says its ok, there are other tools (such as codecov), which are completely thrown by thus and report it as uncovered.
Expected behavior
I would expect, that this line actually would not exist at all.
Reproducer
A commit where it definitely exists: csaf-sbom/kotlin-csaf@11844ec. We are trying to workaround this, so later commits on main might not be used for reproduction.
Reports
see above
Environment
The text was updated successfully, but these errors were encountered: