This message was deleted.

You can enable debugging for the TestKit runner https://docs.gradle.org/current/userguide/test_kit.html#sub:test-kit-debug

@Adam thanks, at least now I know that my plugin is properly applying. I assumed (because I'm a lazy reader), that debug set that as something like a log level... because that's the intuitive

What I usually do in a functional test base class is

if (ManagementFactory.runtimeMXBean.inputArguments.any { it.startsWith('-agentlib:jdwp=') }) {
    runner.withDebug(true)
}

This way when I use

--debug-jvm

or press "Debug" in the IDE,

withDebug(true)

is automatically used and it just works. 🙂

yeah, I was thinking of doing that, or, like, just leaving it on

What IO? It just checks some in-JVM state, doesn't it?

oh, in my case I have to create a git repo

Ah, not I got what you mean

however, looks like

withDebug

doesn't work with configuration cache, so...

Probable because it is more production like to have the test run forked and not in-process?

🤷

Also, if you want to set environment variables this is incompatible with

withDebug