From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I really want to detect when `--tests` has _not_ been passed, so I can   set an env var when this happens. Then the default can be a long timeout but a short timeout can be used when all the tests are being run.

I'm not sure whether you can do that using public API.
If you don't mind using internal API, you can probably get `filter` from the `Test` task, cast it to `DefaultTestFilter` and there check `commandLineIncludePatterns`.

Thanks - unfortunately that seems to be set after the `test {}` block is evaluated. I can see it after being set in a `beforeSuite` listener, but that's too late to set the environment.

Maybe you should just make it explicit, either by some Gradle property, ro by defining two separate tasks.

Probably a simpler solution is just to set the short timeout env var for all tests run by gradle, and tell people to use the JUnit runner in IntelliJ if they want to debug.

set the timeout to long if `System.getProperty("idea.version")`?

I'd rather not tie it to a specific IDE. I suppose the ideal would be to know when you're debugging... I don't know off the top of my head if you can find that out dynamically in a JVM. Will have a look.

hmm. inside the JVM, it should be detectable (since JUnit manages to implement `-Djunit.jupiter.execution.timeout.mode=disabled_on_debug` somehow)

<https://junit.org/junit5/docs/snapshot/user-guide/index.html#writing-tests-declarative-timeouts-mode|https://junit.org/junit5/docs/snapshot/user-guide/index.html#writing-tests-declarative-timeouts-mode>
&gt; A VM runtime is considered to run in debug mode when one of its input parameters starts with `-agentlib:jdwp` or `-Xrunjdwp`.

Here's the code they are using:
<https://github.com/junit-team/junit5/blob/main/junit-platform-commons/src/main/java/org/junit/platform/commons/util/RuntimeUtils.java#L49-L72>

definitely a heuristic since debuggers can be attached via JVMTI or other means, I wonder why there isn't something simple like <https://developer.android.com/reference/android/os/Debug#isDebuggerConnected()> :confused:

but it's probably good enough for your purposes, that's how the IDE probably attaches

I'd hazard a guess they think changing the code because you are debugging may defeat the object - they may have a point!

Thanks all, plenty of stuff to play with.

you're already changing behavior by attaching a debugger - timing, locking, and JIT optimizations - so there's plenty of room for heisenbugs even without an official method for detecting debuggers. but I'm getting a bit far astray from the topic :slightly_smiling_face: