IssueTracker

Thanks for the feedback. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information when it applies if you haven’t already:

1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.

For more information on what’s needed and how to obtain this information please read the guide at https://developer.android.com/studio/report-bugs#studio-bugs

So I made a sample project that demonstrates the issue. You can download it here: https://drive.google.com/file/d/1ZCcEwuqM-m4E5qe94vCn52yWMON8rd5P/view?usp=sharing

If you load the project into Android Studio Chipmunk and above, you will see that the reference to the shared reference in the ExampleIntegrationTest is unresolved. If you comment out the srcDirs line that exposes the shared resource to the unit test, then the androidTest finds the reference. Also, you may have to tweak the AGP version, as I built this project using Dolphin beta01, but the issue is the same in Chipmunk

Please note that in Bumblebee, both test files don't have an issue sharing the resource.

One last thing, sharing test resources is important to avoid duplicate code. Please investigate, you should have enough here to debug the issue.

Any news on this? My StackOverflow question already has 6 upvotes. Looks like this is affecting a decent amount of people (basically anyone with shared resources between unit and instrumented tests).

Here is my StackOverflow post: https://stackoverflow.com/questions/72218645/shared-srcdirs-between-test-and-androidtest-unresolved-references-after-upgrade

(slightly adapted from the comments on 232007221)

Sharing code in this way is not longer supported in the IDE. The reason this was working before is that in pre-chipmunk we ran Android studio import with the intellij options set to create a single module per Gradle project. This option has been removed from IDEA for a good number of years. Importing this way comes with a lot of issues due to the fact that intellij modules can only be set up with two scopes for dependencies and other information, these are compile and test. By default Android modules effectively have three different scopes (which roughly correspond to Gradle source sets per variant) main, unitTest and androidTest. The mapping of these to intellij modules with this option require us to merge the dependencies of unitTest and androidTest. Also any custom source set's need to be merged as well. This caused a lot of incorrect symbol resolution within the editors along with a host of other issues.

In chipmunk we switch to creating a module per (roughly) Gradle source set. This allows us to map the information correctly but unfortunately does result in sharing information between source sets such as this becoming unsupported by the IDE.

To summarize, in order to be correct each source file must only be present in one module otherwise the IDE has no way of knowing which context to use. This can also sometimes result in subtle issues with build. To share sources between test modules you should be able to use put the code in a separate project and consume it as a dependency with both testImplementation and androidTestImplementation.

Thank you for the detailed response.

I also tried the solution you provided at the end of your explanation, but at least for me it didn't work, because my sharedDir test directory code depends on inner app dependencies. I tried creating a test-specific module that depended on my app's module and adding this module as my app's test dependencies (testImplementation & androidTestImplementation) but again I had issues with unresolved references.

I've the same problem as mentioned.

But there is something I don't understand.

Sharing code in this way is not longer supported in the IDE. The reason this was working before is that in pre-chipmunk we ran Android studio import with the intellij options set to create a single module per Gradle project. This option has been removed from IDEA for a good number of years.

I try to open my project in IntelliJ IDEA 2021.2.4 (Community Edition) I don't have any problem. If this way of Sharing code is no longer supported and removed from IDEA for a good number of years shouldn't I get the same errors as Android Studio?

If it is a Java/Kotlin module and you share between main and test it pretends to work by silently ignoring your directory in test source set and it usually works because it depend son main. Try adding more source sets.

If it is an Android module, IDEA bundles some old Android plugin which works the old way for Android regardless of how your project is configured.

Just to clarify, the option has been removed from IDEA in that you can no longer toggle it on and off. The option is still forced on if any Android Gradle project is present as described in #8.

For #6, you should be able to have the following structure of :app <--(implementation) :shared (com.android.library/test) <--((androidT/t)estImplementation) :app. If you are still getting issues with this there may be another problem, which dependency has symbols that aren't been resolved? It might also be related to this.

^^^responding to #9^^^

I will try this again, maybe I made a mistake in my configuration. Thanks for the help

So I tried referencing my app from an android module. Unfortunately, it does not look like you can reference an app as a dependency. I could not use any of the app's inner dependencies.

The solution I came up with is not as nice, but here it is:

1. Place your shared test data in the production code
2. Annotate all files/objects with @VisibleForTesting

Your production code will show a warning if you try referencing the test data, and R8 should remove any code that isn't referenced in production code.

I believe you should be able to add a dependency on the app in another library or test module. See attached project for a simple example. Unfortunately this isn't perfect as current Android studio does not class sources in test modules as test sources. So you might not get symbols showing up when you search test sources only in the IDE.

You will need to switch the version of the Android Gradle plugin used in the attached project to 7.2.0, apologies for this.

Does seem to work with productFlavors...

I've created a com.android.test module with same productFlavors as the app since it was not compiling and the in the app added dependency:

testImplementation project(":sharedTestCode")

androidTestImplementation project(":sharedTestCode")

But none of the code in sharedTestCode is recognized in test and androidTest

I also tried the supplied project example, but as mentioned in #13, the unit tests and integration tests cannot see the shared test class (SharedTestStringClass)

(Keep in mind I am still on Bumblebee testing this)

Thanks for trying, can you see if changing the sharedTestCode project from a com.android.test to a com.android.library and removing the testProjectPath property from the android { ... } configuration helps.

It appears like the dependencies on test modules don't work in version 7.2.0 of the Android Gradle plugin.

#15

It works this way! Tested on Bumblebee and Dolphin beta01. Not sure the exact difference with what I tried before, but now I know it works.

Thanks for your help!

It appears like the dependencies on test modules don't work in version 7.2.0 of the Android Gradle plugin.

I have a question regarding this. I have imported the TestAppDependency.zip project shared in #12 in Android Studio Electric Eel. While the test references are resolved, running the tests is still failing with unresolved references error. But if I change the sharedTestCode to a com.android.library module it works fine. Does AGP doesn't support adding test modules as dependency yet or is the issue related to a specific version of AGP?

There seems to currently be an limitation with dependencies on com.android.test modules. I believe this is present in all current versions of AGP.

The current recommendation is to use a separate com.android.library Gradle project to store any shared code required across test and androidTest.

Note: You will not be able to access things marked internal which would have been accessible before.

I have attached a slightly modified version of the project in #12 which shows the suggested setup for this.

It is also important to mention that the sharedTest module that depends on the :app project MUST define the same flavourDimensions & product flavours as the :app, otherwise it won’t work correctly.

Re #23, you can check http://robolectric.org/blog/2021/10/06/sharedTest/ to learn why we can run code under sharedTest for Robolectric and Espresso. In short words, AndroidJUnit4 will use RobolectricTestRunner or AndroidJUnit4ClassRunner to run tests based on environment. And Robolectric supports Espresso API from 4.x release, so we can run many Espresso tests on Robolectric environment. The sharedTest pattern is a very often used pattern to share UI related test code.