Sergey Shanshin

Replace `runtimeOnly(libs.kover.offline.runtime)` with the `implemetation(libs.kover.offline.runtime)`. Runtime's classes should be included in the application

It may be worth completely rebuild the application, but this error usually indicates that runtime classes are unavailable

Call `clean` Gradle task before test runs

> Interestingly if I comment out below script tests succeed In this case, the instrumentation will not occur and the `.ic` file will not be created. > One question. above...

> Does it mean that I do not have to instrument actually but just run tests and after that run KoverCli report? Because I can see *.ic files being generated...

Could you clarify what is the the number of modified files in your PR? Tens, hundreds or thousands?

It looks like even if you set up offline instrumentation correctly, you will not be able to collect coverage in this way: in ``` tasks.withType(KotlinCompile).configureEach { doLast { def outputDir...

Unfortunately, there is no universal solution here. It all depends on your workflow, CI/CD settings etc. This does not directly apply to Kover, so we cannot directly describe how to...

Closed as answered. Feel free to create new issue if you have any additional questions.

@trietbui85, @woodii, sorry for delayed answer, apparently, I missed the question. Unfortunately, there is no good solution yet. We are currently working on the [potential transfer of code coverage measurement...