Android module's testFixtures do not inherit its own dependencies [353898976]

Assigned

Bug

Status Update

No update yet.

Description

sc...@gmail.com

created issue #1

Jul 18, 2024 03:52PM

It seems that testFixtures source set does not have direct access to main dependencies in Android Library modules.

In the meantime, JVM library modules have such behavior, so there is no need to duplicate dependency entries in Gradle scripts. This not being the same for Android modules seems counter intuitive - other source sets have free access to already declared dependencies - test and androidTest sources get them automatically.

Sample setup:

Gradle module: lib1
android.experimental.enableTestFixturesKotlinSupport=true in gradle.properties

// lib1/build.gradle

plugins {
  id 'com.android.library'
}

android {
  ...

  testFixtures {
    enable = true
  }
}

dependencies {
  implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.8.1"
  // adding this below fixes the issue:
  testFixturesImplementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.8.1"
}

//lib1/src/testFixtures/MyFixture.kt

class MyClass {

  //this fails to compile due to missing dependency 👇
  val stateFlow = MutableStateFlow<String()
}

AGP: 8.5.1 Gradle: 8.9

Comments

sa...@google.com <sa...@google.com> Jul 20, 2024 01:21AM

Assigned to an...@google.com.

hu...@google.com <hu...@google.com> Jul 24, 2024 09:35PM

Reassigned to cm...@google.com.

mr...@gmail.com <mr...@gmail.com> #2Aug 8, 2024 05:46PM

I tried adding screenshotTestImplementation(libs.androidx.window) but it didn't fix it.

ni...@hinge.co <ni...@hinge.co> #3Aug 13, 2024 08:47PM

This is likely a duplicate of b/388773416. Could you try adding libs.androidx.window dependency to implementation to see if it works?

eu...@gmail.com <eu...@gmail.com> #4Aug 14, 2024 08:42AM

Thanks for the workaround. In my case I also need to extend from testImplementation.

Not sure if this ticket will cover this as well.

eu...@gmail.com <eu...@gmail.com> #5Aug 14, 2024 09:50AM

Ah, and this workaround fails the check<*>AndroidTestDuplicateClasses - we use test fixtures also for instrumental tests.

Checking if i can do something with it.

Issue 353898976