How can you use WorkerAction with the TestListener...
# community-supportp
Philip W
05/28/2025, 7:19 AMHow can you use WorkerAction with the TestListener? I don't want to use a main function and pass all the parameters untyped
v
Vampire
05/28/2025, 7:38 AMMind elaborating what you are talking about?
At least me I have no idea what you mean.
p
Philip W
05/28/2025, 7:41 AMOh okay. I use a custom TestListener https://docs.gradle.org/current/kotlin-dsl/gradle/org.gradle.api.tasks.testing/-abstract-test-task/add-test-listener.html?query=open%20fun%20addTestListener(listener:%20TestListener) with an injected
ExecOperationsWorkerExecutorPhilip W
05/28/2025, 7:43 AMThe ExecOperations will be run synchronously and it blocks the current listener, like when called in
afterSuitev
Vampire
05/28/2025, 7:44 AMAH, ok, did you just try it? 🙂
Unfortunately it is not really documented what you can legally inject where.
p
Philip W
05/28/2025, 7:44 AMNope, not yet, because testing it is little bit painful, but yeah will do it
v
Vampire
05/28/2025, 7:45 AMVampire
05/28/2025, 7:49 AMBtw. how do you instantiate the listener?
The method you mentioned takes a concrete instance.
p
Philip W
05/28/2025, 7:50 AMobjects.newInstance(UploadXRayResults::class)v
Vampire
05/28/2025, 8:05 AMAnd why is it hard to test?
Copy code
abstract class MyTestListener : TestListener {
@get:Inject
abstract val execOperations: ExecOperations
@get:Inject
abstract val workerExecutor: WorkerExecutor
init {
println(execOperations)
println(workerExecutor)
}
override fun beforeSuite(suite: TestDescriptor?) = Unit
override fun afterSuite(suite: TestDescriptor?, result: TestResult?) = Unit
override fun beforeTest(testDescriptor: TestDescriptor?) = Unit
override fun afterTest(testDescriptor: TestDescriptor?, result: TestResult?) = Unit
}
tasks.test {
addTestListener(objects.newInstance<MyTestListener>())
}Vampire
05/28/2025, 8:05 AM Copy code
org.gradle.process.internal.DefaultExecOperations_Decorated@1dd1c241
org.gradle.workers.internal.DefaultWorkerExecutor_Decorated@4613c0c6p
Philip W
05/28/2025, 9:08 AMOh... you are right, I could test it inline, fail...
Philip W
05/28/2025, 9:08 AMI was about to rewrite my whole implementation...
Philip W
05/28/2025, 9:08 AMThank you!
👌 1
Philip W
06/03/2025, 8:55 AMHm, now I get this error:
An attempt was made to submit work from a thread not managed by Gradle. Work may only be submitted from a Gradle-managed thread.v
Vampire
06/03/2025, 8:59 AMHm, maybe a bug?
Sounds like the thread should be managed by Gradle.
Or it is not supported, no idea.
Maybe check on which thread this actually is called?
p
Philip W
06/03/2025, 9:26 AMHm, it does work with kotlin.lazy... Still a bug:
Copy code
abstract class MyTestListener : TestListener {
@get:Inject
abstract val workerExecutor: WorkerExecutor
private val s by lazy {
val s = workerExecutor.noIsolation()
s.submit(FooWork::class) {
}
s.await()
42
}
override fun beforeSuite(suite: TestDescriptor) = Unit
override fun afterSuite(suite: TestDescriptor, result: TestResult) {
println(s)
}
override fun beforeTest(testDescriptor: TestDescriptor) = Unit
override fun afterTest(testDescriptor: TestDescriptor, result: TestResult) = Unit
}
abstract class FooWork : WorkAction<WorkParameters.None> {
override fun execute() {
println("Running Foo work")
}
}
tasks.test {
addTestListener(objects.newInstance<MyTestListener>())
}Philip W
06/03/2025, 9:30 AMLooks like the JUnit framework calls the
afterSuitePhilip W
06/03/2025, 9:34 AM4 Views