This message was deleted Gradle Community #community-support

Join Slack

This message was deleted.

# community-support

Slackbot

01/25/2023, 5:57 PM

This message was deleted.

Thomas Broyer

01/25/2023, 6:04 PM

You have to declare the

functionalTest

compilation as a associated with the main compilation:

Copy code

kotlin.target.compilations.named("functionalTest") {
    associateWith(kotlin.target.compilations["main"])
}

The Kotlin plugin does that automatically for the

test

source set, but you have to do it manually for any other source set (e.g. testing suites)

thank you 1

Javi

01/25/2023, 6:12 PM

does

compilations

exist outside of KMP?

Javi

01/25/2023, 6:13 PM

ah okay, it exists on

KotlinJvmProjectExtension

too, but not on

KotlinProjectExtension

Javi

01/25/2023, 6:24 PM

testFixtures

by default has the same problem, I guess it is an intended behavior, right?

🤷 1

Javi

01/25/2023, 6:51 PM

I tried to do the same with

testFixtures

but no luck 🤷

Copy code

kotlin.target.compilations.named("functionalTest") {
    associateWith(kotlin.target.compilations["testFixtures"])
}

Javi

01/25/2023, 7:22 PM

Do I need to do something special for getting plugin under test working?

Copy code

Test runtime classpath does not contain plugin metadata file 'plugin-under-test-metadata.properties'
org.gradle.testkit.runner.InvalidPluginMetadataException: Test runtime classpath does not contain plugin metadata file 'plugin-under-test-metadata.properties'

Copy code

val testPluginClasspath: Configuration =
    configurations.create("testPluginClasspath")

dependencies {
    for (dependency in pluginUnderTestDependencies) {
        testPluginClasspath(dependency)
    }
}

tasks.withType<PluginUnderTestMetadata>().configureEach { metadata ->
    metadata.pluginClasspath.from(testPluginClasspath)
}

Javi

01/25/2023, 7:22 PM

It was working on

test

source set, but fails on

functionalTest

one

ephemient

01/25/2023, 7:24 PM

Copy code

kotlin.target.compilations {
    val main by getting
    val testFixtures by getting {
        associateWith(main)
    }
    named("functionalTest") {
        associateWith(main)
        associateWith(testFixtures)
    }
}

compiles fine for me with access to

internal

across source sets, the only problem is the IDE not recognizing it

ephemient

01/25/2023, 7:38 PM

you can use

@file:Suppress("INVISIBLE_REFERENCE", "INVISIBLE_MEMBER")

to bypass

internal

protection as well. the IDE won't help with auto-complete but it'll stop showing red errors

Thomas Broyer

01/25/2023, 8:39 PM

Wrt plugin-under-test-metadata:

Copy code

gradlePlugin {
    testSourceSets(project.sourceSets["functionalTest"])
}

thank you 1

Javi

01/26/2023, 12:16 AM

Looks like it is getting cached and it passes even when it should fail. I run from the IDE and it fails, but when running it via terminal it passes and the tests are not running. Should I config something more?

Javi

01/26/2023, 12:17 AM

Indeed it only fails from IDE, from terminal even using

--rerun-tasks

it passes 🤔

Javi

01/26/2023, 12:22 AM

Looks like it was fixed alone, some weird cache I guess

Thomas Broyer

01/26/2023, 7:31 AM

You don't delegate to Gradle when running from the IDE? (assuming you're using some flavor of JetBrains' IDE, no idea how things work in other IDEs)

Javi

01/26/2023, 9:14 AM

Yeah, that was the weird part, IDE uses Gradle and it was failing correctly but via terminal it was passing. But looks like it is fixed

Open in Slack

Previous Next