not kotest 100% related but

Kover

. Does anyone know how to set up configuration in order run tests each time a coverage report task is called?

I think you could do something like

tasks.withType<KoverReportTask>().configureEach {
   dependsOn(tasks.named("test"))
}

but I would ask in #gradle

Kover tasks are already set to run if you run the test task. Which is the use case to do the reversed flow?

oh nice! well I didn’t know that. In that case I wouldn’t need to do so 😄

Anyway I would check it with dry run and 0.7.0 alpha, as I haven’t checked if it will do the same with the new huge refactor

Kover tasks are already set to run if you run the test task. Which is the use case to do the reversed flow?

really? I was thinking of looking at moving from jacoco to kover because jacoco is not very precise with kotlin code, but I don’t think it’s right to run coverage every time you run tests. at least, I don’t think it’s common to run all tests all the time, that is more CI job, but if you don’t run all the tests coverage is just a waste of time

I asume that this is somehow configurable, can’t ensure tho

Gradle allow disabling tasks easily, so it is easy to disable that behavior

disclaimer: I did not start to look into anything yet 😄

I just tryed new kover 0.7, way easier to config

anyway I think it doesn’t consume a lot of time

this is the only

kover

related task in the output:

:feature:widgets:koverFindJar SKIPPED

dry run is to know which tasks would run

Ok let me try to clean everything and re-run

but without dry run

I doesn’t I had to generate them manually

you mean you need to call the kover task manually, right?

KoverReportTask

not present 😕

Oh, I'm using Kover 0.6.x. Maybe it's changed name

they renamed a lot of things in 0.7.0

wait a second

tbh I haven’t used kover with android, so I am not sure about the behavior of kover on that land