Tests are not executed #391

vassilisimon · 2023-05-31T09:00:22Z

Hello,

When I run :app:koverXmlReport I always get:

Task :app:koverXmlReport SKIPPED
Task 'koverXmlReport' will be skipped because no tests were executed

So also sonarqube complains:

No coverage report can be found with sonar.coverage.jacoco.xmlReportPaths='/builds/os/now/abc-android//build/reports/kover/report.xml'. Using default locations: target/site/jacoco/jacoco.xml,target/site/jacoco-it/jacoco.xml,build/reports/jacoco/test/jacocoTestReport.xml

My minimal setup:

build.gradle.kts (:app)

plugins {
... 
id("org.jetbrains.kotlinx.kover")
}

dependencies {
    kover(project(":ui:mobile:xy"))
}

koverReport {
    // filters for all report types of all build variants
    filters {
        excludes {
            classes(
                "*Fragment",
                "*Fragment\$*",
                "*Activity",
                "*Activity\$*",
                "*.databinding.*",
                "*.BuildConfig"
            )
        }
    }
    defaults {
        xml {
            setReportFile(layout.buildDirectory.file("reports/kover/report.xml"))
        }
    }
}

build.gradle.kts (root)

plugins {
id("org.jetbrains.kotlinx.kover") version 0.7.0
}

subprojects {
apply(plugin = "org.jetbrains.kotlinx.kover")
...
}

sonarqube {
    properties {
        property("sonar.coverage.jacoco.xmlReportPaths", "$buildDir/reports/kover/report.xml")
    }
}

tasks.findByName("sonarqube")?.dependsOn("koverXmlReport")

Do you have an idea how to trigger the tests?

The text was updated successfully, but these errors were encountered:

realdadfish · 2023-05-31T15:08:08Z

Is this an Android project by any chance (determining from the dependency "ui:mobile:xy")? If so, you need to use

koverReport {
     androidReports("<yourBuildVariantHere>") {
         // report configuration
     }
}

This triggers the tests for me. The task that you need to execute then is named koverXmlReport<YourBuildVariant>.

vassilisimon · 2023-05-31T16:25:04Z

Is this an Android project by any chance (determining from the dependency "ui:mobile:xy")? If so, you need to use
koverReport {
     androidReports("<yourBuildVariantHere>") {
         // report configuration
     }
}
This triggers the tests for me. The task that you need to execute then is named koverXmlReport<YourBuildVariant>.

It's an android project, yes.
Thanks for your help, I added this in the defaults block:
mergeWith("debug")
but now I get this problem:
#388

How can I apply the kover plugin after AGP? It's currently applied in the subprojects block.

And if I use the androidReports block instead of mergeWith() then I can't find the koverXmlReportDebug gradle task.

realdadfish · 2023-05-31T16:38:56Z

I think there is a workaround mentioned in #362

vassilisimon · 2023-05-31T16:52:49Z

Still not clear to me where/what to execute in project.afterEvaluate { ... }.
I tried
subprojects { project.afterEvaluate { apply(plugin = "org.jetbrains.kotlinx.kover") } },

but I still get:
Android build variant 'debug' was not found - it is impossible to add it to the default report
because of mergeWith("debug") which is in the koverReport block.

shanshin · 2023-05-31T17:56:24Z

Hi,
@vassilisimon , is using tasks.findByName("sonarqube")?.dependsOn("koverXmlReportDebug") and either calling :app:koverXmlReportDebug applicable to you?

shanshin · 2023-05-31T17:58:00Z

afterEvaluate { It may not solve similar problems, because it will be executed in the same order in which the plugins were applied.

vassilisimon · 2023-05-31T18:08:44Z

Hi,
@vassilisimon , is using tasks.findByName("sonarqube")?.dependsOn("koverXmlReportDebug") and either calling :app:koverXmlReportDebug applicable to you?

I tried it also, but it didn't work, as it can't find a gradle task called "koverXmlReportDebug".

shanshin · 2023-05-31T19:19:41Z

How can I apply the kover plugin after AGP? It's currently applied in the subprojects block.

At the moment, the most effective workflow is to apply the plugin explicitly in each project, instead of subprojects.

So you can explicitly specify the order of applying of plugins, e.g.

plugins {
    id ("com.android.application")
    id ("org.jetbrains.kotlin.android")
    id ("org.jetbrains.kotlinx.kover")
}

vassilisimon · 2023-05-31T19:27:50Z

How can I apply the kover plugin after AGP? It's currently applied in the subprojects block.

At the moment, the most effective workflow is to apply the plugin explicitly in each project, instead of subprojects.

So you can explicitly specify the order of applying of plugins, e.g.
plugins {
    id ("com.android.application")
    id ("org.jetbrains.kotlin.android")
    id ("org.jetbrains.kotlinx.kover")
}

Okay, it's just a bit of tedious work, we have >200 modules.

And that would be the next question, do we have also to add this line for each module?

kover(project(":ui:mobile:module_1")
kover(project(":ui:mobile:module_n")
kover(project(":ui:tv:module_1")
kover(project(":ui:tv:module_n")

Right?
And is there a better solution?

shanshin · 2023-05-31T19:44:08Z

Okay, it's just a bit of tedious work, we have >200 modules.

Perhaps in this case it is better to wait for fix #362.

And that would be the next question, do we have also to add this line for each module?

The dependency must be specified only in project, in which the merged report will be generated

At the same time, you can use subprojects to add dependencies, because this does not add any actions to the afterEvaluate, unlike applying a plugin.

vassilisimon · 2023-06-01T09:02:15Z

Thanks, then I'll wait for the fix of #362.

shanshin · 2023-06-27T16:03:42Z

@vassilisimon, could you please check version 0.7.2?

vassilisimon · 2023-06-29T09:42:50Z

Updated setup:

build.gradle.kts (:app)

plugins {
... 
    id("org.jetbrains.kotlinx.kover")
}

dependencies {
    kover(project(":ui:mobile:xy"))
    kover(project(":x:y:z"))
    ... 200 more
}

koverReport {
    androidReports("betaPreProdRelease") {
        // filters for all report types for betaPreProdRelease builds
        filters {
            excludes {
                classes(
                    "*Fragment",
                    "*Fragment\$*",
                    "*Activity",
                    "*Activity\$*",
                    "*.databinding.*",
                    "*.BuildConfig"
                )
            }
        }
    }
}

build.gradle.kts (root)

plugins {
    id("org.jetbrains.kotlinx.kover") version 0.7.2
}

subprojects {
    apply(plugin = "org.jetbrains.kotlinx.kover")
...
}

sonarqube {
    properties {
        property("sonar.coverage.jacoco.xmlReportPaths", "$rootDir/app/build/reports/kover/report.xml")
    }
}

tasks.findByName("sonar")?.dependsOn(":app:koverXmlReport")

With 0.7.2 it creates now a report in app/build/reports/kover/report.xml

But I've still 2 problems:

Kover doesn't execute all unit tests we have, only ~500 out of ~3200).
Sonarqube can't find any data regarding coverage.

** Edit:

If I use :app:koverXmlReportBetaPreProdDebug, then it runs all tests, but now I get:

* What went wrong:
Execution failed for task ':app:koverXmlReportBetaPreProdDebug'.
> Cannot access input property 'externalSources$kover_gradle_plugin' of task ':app:koverXmlReportBetaPreProdDebug'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). See https://docs.gradle.org/8.1.1/userguide/incremental_build.html#disable-state-tracking for more details.
   > Failed to create MD5 hash for file '/usr/bin/sudo' as it does not exist.

shanshin · 2023-06-30T09:16:43Z

Kover doesn't execute all unit tests we have, only ~500 out of ~3200).

It looks like this is because the tests were run only for JVM targets.
In order to run tests for any build variant when executing koverXmlReport, it is worth adding mergeWith("...")

Failed to create MD5 hash for file '/usr/bin/sudo' as it does not exist.

Have you added kover(project("...")) dependencies for the:app project?

vassilisimon · 2023-07-04T10:29:44Z

Have you added kover(project("...")) dependencies for the:app project?

Yes, for all modules (build.gradle.kts (:app)):

dependencies {
    kover(project(":ui:mobile:xy"))
    kover(project(":x:y:z"))
    ... 200 more
}

It looks like this is because the tests were run only for JVM targets. In order to run tests for any build variant when executing koverXmlReport, it is worth adding mergeWith("...")

I tried it:

koverReport {
    defaults {
        mergeWith("betaPreProdDebug")
    }
}

but same issue:

* What went wrong:
Execution failed for task ':app:koverXmlReport'.
> Cannot access input property 'localSources$kover_gradle_plugin' of task ':app:koverXmlReport'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). See https://docs.gradle.org/8.1.1/userguide/incremental_build.html#disable-state-tracking for more details.
   > Failed to create MD5 hash for file '/usr/bin/sudo' as it does not exist.

shanshin · 2023-07-04T11:00:22Z

* What went wrong:
Execution failed for task ':app:koverXmlReport'.
> Cannot access input property 'localSources$kover_gradle_plugin' of task ':app:koverXmlReport'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). See https://docs.gradle.org/8.1.1/userguide/incremental_build.html#disable-state-tracking for more details.
   > Failed to create MD5 hash for file '/usr/bin/sudo' as it does not exist.

Could you show the contents of the app/build/kover/default.artifact file for this case?
I wonder if there is a mention of /usr/bin/sudo there

vassilisimon · 2023-07-10T17:45:53Z

The content is too large, but there is no mention of /usr/bin/sudo.

We have for now a workaround for this problem:

subprojects {
    project.tasks.whenTaskAdded {
        if (this.name.toLowerCaseAsciiOnly().contains("koverxmlreport")) {
            this.doNotTrackState("Dont support state tracking")
        }
...
}

tasks.findByName(Tasks.KOVER_XML_REPORT)?.doNotTrackState("sudo issues")

shanshin · 2023-07-12T10:31:15Z

@vassilisimon

this.doNotTrackState("Dont support state tracking")

With this setting, the tests run successfully and a correct report is generated?

vassilisimon · 2023-07-12T14:47:54Z

@shanshin Exactly.

shanshin · 2023-07-13T10:26:59Z

In this case, I think the current issue should be closed.

if the specified workaround will cause any inconvenience, then it is worth create a separate issue for this.
But since this is a very rare problem, in this case we need more information about the environment to understand the reasons why Gradle processes the /usr/bin/sudo file.

vassilisimon · 2023-07-13T13:33:36Z

As it's a closed source project I can't provide more information here. At most in a private video/screen share session.

But thanks for your time & help!

raamcosta · 2023-07-18T16:04:20Z

I also got this error

Execution failed for task ':app:koverXmlReportMockDebug'.
Cannot access input property 'externalSources$kover_gradle_plugin' of task ':app:koverXmlReportMockDebug'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). See https://docs.gradle.org/8.1/userguide/incremental_build.html#disable-state-tracking for more details.
Failed to create MD5 hash for file '/usr/bin/sudo' as it does not exist.

Besides, If I apply a workaround for task koverHtmlReport the task never finishes.

I also got this weird behavior the first couple of times, that Android Studio was asking for all kinds of permissions to access stuff on my mac.

EDIT: Some more info.

If I run koverPrintCoverageMockDebug (with the above workaround for disabling state tracking) I get an output, but before, I see this:

Task :app:koverLogMockDebug
[2023.07.18 17:16:49] (Coverage): Failed to check raw report file: java.io.FileNotFoundException: . (Is a directory)
[2023.07.18 17:16:49] (Coverage): Failed to load coverage data from file: /Users/rafael.costa/.gradle/daemon/8.1/.: java.io.FileNotFoundException: . (Is a directory)

If I run koverXmlReportMockDebug, I also get an xml, so for me, the stated workaround seems to mostly work except for html report which seem to never finish. Of course I don't know if there is still an issue that impacts accuracy that we're just masking with this state track disabling 🤔

raamcosta · 2023-07-19T18:09:15Z

What I got today:

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:koverVerify'.
Cannot access input property 'localSources$kover_gradle_plugin' of task ':app:koverVerify'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). See https://docs.gradle.org/8.1/userguide/incremental_build.html#disable-state-tracking for more details.
java.nio.file.FileSystemException: /System/Volumes/Data/home: Operation not permitted

Notice I am running koverVerify without any specification of a build variant, so it is trying to run on all modules even on non-android ones.
It seems like when I add the previously mentioned workaround it doesn't disable state tracking for non-android modules 🤔

I'm sorry I will add here as I go, I hope it can be somehow a bit helpful 🙏

EDIT:

Ok, so I edited the workaround described by @vassilisimon to this:

allprojects {
    apply(plugin = rootProject.libs.plugins.kover.get().pluginId)

    project.tasks.forEach {
        if (it.name.contains("kover", ignoreCase = true)) {
            println("calling doNotTrackState: MODULE ${project.name} TASK ${it.name}")
            it.doNotTrackState("Dont support state tracking")
        }
    }
}

And now it does disable track state on all kover's tasks. But now I have another error:

EXPAND ERROR

FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':app:koverLog' (type 'KoverFormatCoverageTask').
  - Gradle detected a problem with the following location: '/'.
    
    Reason: Task ':app:koverLog' uses this output of task ':compileJava' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':compileJava' as an input of ':app:koverLog'.
      2. Declare an explicit dependency on ':compileJava' from ':app:koverLog' using Task#dependsOn.
      3. Declare an explicit dependency on ':compileJava' from ':app:koverLog' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/'.
    
    Reason: Task ':app:koverLog' uses this output of task ':compileTestJava' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':compileTestJava' as an input of ':app:koverLog'.
      2. Declare an explicit dependency on ':compileTestJava' from ':app:koverLog' using Task#dependsOn.
      3. Declare an explicit dependency on ':compileTestJava' from ':app:koverLog' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/'.
    
    Reason: Task ':app:koverLog' uses this output of task ':compileKotlin' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':compileKotlin' as an input of ':app:koverLog'.
      2. Declare an explicit dependency on ':compileKotlin' from ':app:koverLog' using Task#dependsOn.
      3. Declare an explicit dependency on ':compileKotlin' from ':app:koverLog' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/'.
    
    Reason: Task ':app:koverLog' uses this output of task ':compileTestKotlin' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':compileTestKotlin' as an input of ':app:koverLog'.
      2. Declare an explicit dependency on ':compileTestKotlin' from ':app:koverLog' using Task#dependsOn.
      3. Declare an explicit dependency on ':compileTestKotlin' from ':app:koverLog' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/'.
    
    Reason: Task ':app:koverLog' uses this output of task ':test' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':test' as an input of ':app:koverLog'.
      2. Declare an explicit dependency on ':test' from ':app:koverLog' using Task#dependsOn.
      3. Declare an explicit dependency on ':test' from ':app:koverLog' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

It looks a bit more informative 🤞
Notice I get these errors when it tries to do something with "app" module which is the main one that depends on all others. I do have the dependencies block where I define kover dependencies on other modules.

raamcosta · 2023-07-21T14:01:51Z

New update:

I did what the above error said to do and I managed to do everything except html report which fails with this error:

[2023.07.21 14:00:26] (Coverage): Failed to check raw report file: java.io.FileNotFoundException: /home/runner/.gradle/daemon/8.1 (Is a directory)
> Task :app:koverHtmlReport
Kover: HTML report for ':app' file:///home/runner/work/my-projectn/my-project/app/build/reports/kover/html/index.html
[2023.07.21 14:00:28] (Coverage): Failed to load coverage data from file: /home/runner/.gradle/daemon/8.1: java.io.FileNotFoundException: /home/runner/.gradle/daemon/8.1 (Is a directory)

In case it helps anyone else, here's what I ended with:

allprojects {
    apply(plugin = rootProject.libs.plugins.kover.get().pluginId)

    project.tasks.whenTaskAdded {
        if (this.name.startsWith("kover", ignoreCase = true)) {
            this.doNotTrackState("Dont support state tracking")
        }
    }

    project.tasks.forEach {
        if (it.name.startsWith("kover", ignoreCase = true)) {
            it.doNotTrackState("Dont support state tracking")
        }

        if (project.name == "app" && it.name == "koverLog") {
            it.mustRunAfter(rootProject.tasks.getByName("compileJava"))
            it.mustRunAfter(rootProject.tasks.getByName("compileTestJava"))
            it.mustRunAfter(rootProject.tasks.getByName("test"))
            it.mustRunAfter(rootProject.tasks.getByName("koverLog"))
            it.mustRunAfter(rootProject.tasks.getByName("koverGenerateArtifact"))
        }
    }
}

vassilisimon added Question Support request issue type S: untriaged Status: issue reported but unprocessed labels May 31, 2023

vassilisimon assigned shanshin May 31, 2023

shanshin added S: waiting for clarification Status: additional information required to proceed and removed S: untriaged Status: issue reported but unprocessed labels May 31, 2023

shanshin closed this as completed Sep 21, 2023

shanshin mentioned this issue Oct 11, 2023

[0.7.4] Cannot access input property externalReports$kover_gradle_plugin of task #478

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tests are not executed #391

Tests are not executed #391

vassilisimon commented May 31, 2023 •

edited

Loading

realdadfish commented May 31, 2023

vassilisimon commented May 31, 2023 •

edited

Loading

realdadfish commented May 31, 2023

vassilisimon commented May 31, 2023 •

edited

Loading

shanshin commented May 31, 2023

shanshin commented May 31, 2023

vassilisimon commented May 31, 2023 •

edited

Loading

shanshin commented May 31, 2023 •

edited

Loading

vassilisimon commented May 31, 2023 •

edited

Loading

shanshin commented May 31, 2023

vassilisimon commented Jun 1, 2023 •

edited

Loading

shanshin commented Jun 27, 2023

vassilisimon commented Jun 29, 2023 •

edited

Loading

shanshin commented Jun 30, 2023 •

edited

Loading

vassilisimon commented Jul 4, 2023 •

edited

Loading

shanshin commented Jul 4, 2023

vassilisimon commented Jul 10, 2023

shanshin commented Jul 12, 2023

vassilisimon commented Jul 12, 2023

shanshin commented Jul 13, 2023 •

edited

Loading

vassilisimon commented Jul 13, 2023 •

edited

Loading

raamcosta commented Jul 18, 2023 •

edited

Loading

raamcosta commented Jul 19, 2023 •

edited

Loading

raamcosta commented Jul 21, 2023 •

edited

Loading

Tests are not executed #391

Tests are not executed #391

Comments

vassilisimon commented May 31, 2023 • edited Loading

realdadfish commented May 31, 2023

vassilisimon commented May 31, 2023 • edited Loading

realdadfish commented May 31, 2023

vassilisimon commented May 31, 2023 • edited Loading

shanshin commented May 31, 2023

shanshin commented May 31, 2023

vassilisimon commented May 31, 2023 • edited Loading

shanshin commented May 31, 2023 • edited Loading

vassilisimon commented May 31, 2023 • edited Loading

shanshin commented May 31, 2023

vassilisimon commented Jun 1, 2023 • edited Loading

shanshin commented Jun 27, 2023

vassilisimon commented Jun 29, 2023 • edited Loading

shanshin commented Jun 30, 2023 • edited Loading

vassilisimon commented Jul 4, 2023 • edited Loading

shanshin commented Jul 4, 2023

vassilisimon commented Jul 10, 2023

shanshin commented Jul 12, 2023

vassilisimon commented Jul 12, 2023

shanshin commented Jul 13, 2023 • edited Loading

vassilisimon commented Jul 13, 2023 • edited Loading

raamcosta commented Jul 18, 2023 • edited Loading

raamcosta commented Jul 19, 2023 • edited Loading

raamcosta commented Jul 21, 2023 • edited Loading

vassilisimon commented May 31, 2023 •

edited

Loading

vassilisimon commented May 31, 2023 •

edited

Loading

vassilisimon commented May 31, 2023 •

edited

Loading

vassilisimon commented May 31, 2023 •

edited

Loading

shanshin commented May 31, 2023 •

edited

Loading

vassilisimon commented May 31, 2023 •

edited

Loading

vassilisimon commented Jun 1, 2023 •

edited

Loading

vassilisimon commented Jun 29, 2023 •

edited

Loading

shanshin commented Jun 30, 2023 •

edited

Loading

vassilisimon commented Jul 4, 2023 •

edited

Loading

shanshin commented Jul 13, 2023 •

edited

Loading

vassilisimon commented Jul 13, 2023 •

edited

Loading

raamcosta commented Jul 18, 2023 •

edited

Loading

raamcosta commented Jul 19, 2023 •

edited

Loading

raamcosta commented Jul 21, 2023 •

edited

Loading