Róbert Papp

The point of test suites is to separate the suites. In Android this comes with different tech, in JVM too, but only sometimes. Screenshot tests are a very specific type...

No way, levels are dropping faster than new ones coming out...

Nice idea! Doesn't sound that bad as it can be scripted, and ran overnight (few GBs of internet traffic) :)

Also potentially "doable" from docs? https://developer.android.com/ndk/downloads/revision_history.html

I think the issue might be visibility: https://github.com/cdsap/Talaiot/blob/33a6e36c798686630308252eed1fc8f68c623fa6/library/plugins/base/base-plugin/src/main/java/io/github/cdsap/talaiot/plugin/base/BaseConfiguration.kt#L8 extends https://github.com/cdsap/Talaiot/blob/33a6e36c798686630308252eed1fc8f68c623fa6/library/core/talaiot/src/main/kotlin/io/github/cdsap/talaiot/publisher/PublishersConfiguration.kt#L5 which means `BaseConfiguration`'s API contains the superclass `PublishersConfiguration`. but it's not exposed as a dependency (`api(...)`): https://github.com/cdsap/Talaiot/blob/33a6e36c798686630308252eed1fc8f68c623fa6/library/plugins/base/base-plugin/build.gradle.kts#L17

Interesting workaround! Thanks for sharing. I also found the same problem: https://github.com/renovatebot/renovate/discussions/29265, any chance you're coming from Renovate too?

> But why mutliple test dispatchers are needed? Why one is not enough? What practical problem is being solved by using multiple test dispatchers? @elizarov on Android Espresso UI tests,...

@pyricau is there a planned 2.x maintenance release? or should we be using 3.x alphas?

> I have attempted to set that property myself on a normal unit test run using ./gradlew testDebugUnitTest -Dpaparazzi.test.verify=true but it doesn't seem to have any effect. The system property...

I really like this view and use it on all my projects: https://github.com/TWiStErRob/net.twisterrob.gradle/runs/15212418581 accessible from a PR/commit with one click:  I would go insane without it, logs are hard...