`androidAndroidTest` .. ha
# multiplatformx
xxfast
04/27/2021, 9:10 AMandroidAndroidTests
Sebastian Sellmair [JB]
04/27/2021, 10:12 AMUnfortunate 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!
👍 2
x
xxfast
04/27/2021, 10:15 AMunderstandable 🙂 i think android should’ve gone with
instrumentationTestj
jw
04/27/2021, 12:27 PMit was originally called that and was changed to androidTest in the very very early AGP 0.x days
jw
04/27/2021, 12:29 PMLooks like it was instrumentTest. I misremembered.
In 0.9.0 notes http://tools.android.com/tech-docs/new-build-system
🙌 1
x
xxfast
12/28/2022, 9:58 PMFinally solved in 1.8 https://kotlinlang.org/docs/whatsnew18.html#kotlinsourceset-naming-schema
j
jw
12/28/2022, 10:14 PMOof that's a bad change
jw
12/28/2022, 10:14 PMUnit is a type of test, instrumented is a mechanism
jw
12/28/2022, 10:14 PMYou can run unit tests within instrumentation
jw
12/28/2022, 10:16 PMJVM test or host test describe the execution mechanism similar to what instrumented describes
jw
12/28/2022, 10:16 PMYour host-side tests may also not be unit tests but functional or integration tests
x
xxfast
12/29/2022, 8:45 AMLooks like another issue for #naming
s
Sebastian Sellmair [JB]
12/29/2022, 6:02 PMKotlin Multiplatform just follows the naming schema from Android. Inventing just another terminology would be the worse option.
Sebastian Sellmair [JB]
12/29/2022, 6:02 PMThe naming change also fixes issues under the hood, where names were wrongly clashing.
Sebastian Sellmair [JB]
12/29/2022, 6:03 PM@jw just out curiosity: if you would be the AGP team: how would you name the source sets?
j
jw
01/04/2023, 12:59 AMInstrumented 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.
jw
01/04/2023, 2:02 AMMaybe we can @-mention Xav tomorrow and get his take? I remember being involved on adt-dev@ list when they switched from instrumentTest to androidTest as well.
15 Views