Sergey Shanshin
Sergey Shanshin
**What is your use-case and why do you need this feature?** Property `variantName` will help to filter Kover tasks by selecting those that relate to specific variant. So, to find...
When generating HTML reports and during verification, any nested classes are analyzed and displayed separately. From the point of view of Kotlin code, this is not entirely correct, because these...
**What is your use-case and why do you need this feature?** If the testing does not take place in one build run, but is distributed over several builds, for example,...
It is necessary to figure out how to motivate to use the beta version of DSL. Independently try to implement the beta version in popular Android projects in order to...
The current HTML report one is poorly suited for displaying the coverage of code written in Kotlin. It is necessary to think over a new design and implement code to...
At the moment, Kover Coverage Tool only supports JVM instrumentation. Accordingly, only coverage from JVM tests gets into the reports. To fully support Kotlin Multi-Platform, it is necessary to implement...
TBD
The current implementation of the IntelliJ Coverage Agent allows you to run only Java tests running on the same machine where the Gradle build is running. To implement coverage measurement...
To plan further actions, it is necessary to evaluate the current interaction between Kover Gradle Plugin and [kotlinFixtures](https://github.com/appmattus/kotlinfixture). After review, it is necessary to develop a plan for modification of...
In some cases, it is convenient to exclude from the report all classes inherited from one parent, or implementing a specific interface. This is more convenient than annotating several classes...