androidAndroidTest

.. ha

Unfortunate naming. {targetName}{android source set name} targetName = ‘android’ android source set name = ‘androidTest’ Will be solved in a some bright future, that we’re actively working on!

understandable 🙂 i think android should’ve gone with

instrumentationTest

similar to ios

it was originally called that and was changed to androidTest in the very very early AGP 0.x days

Finally solved in 1.8 https://kotlinlang.org/docs/whatsnew18.html#kotlinsourceset-naming-schema

Oof that's a bad change

Looks like another issue for #naming

Kotlin Multiplatform just follows the naming schema from Android. Inventing just another terminology would be the worse option.

Instrumented is a good word, but not well defined for an average developer. I'd wager most don't know the instrumentation class in the Android SDK or what it's function is. It's also complicated by Robolectric running instrumentation. I tend to say host vs. device. Both are words people should be able to understand. Device covers physical and emulator pretty well, but fails on Chromebooks where the host is effectively also the device. That's rare enough that I'm okay with it (and most developers probably understand Android apps run in an emulator-like simulator on Chromebooks so still kinda works) Host isn't perfect but it has the benefit of being short. The ideal name for host is really jvmTest, or androidJvmTest in MPP. The ideal name for device is dalvikTest or artTest. The problem with these ideal names is that they're jargon you probably don't know when you're getting started, so there's an ordering problem for learning. That's why when I talk about tests I use host and device, and it would be my vote.