Studio not correctly handling testFixture srcSet of jar gradle modules. [139762443]

Fixed

Bug

Reviewed (L1)

Status Update

No update yet.

Description

tr...@gmail.com

created issue #1

Aug 20, 2019 10:42PM

Version of Gradle Plugin: 3.6.0-alpha06
Version of Gradle: 5.6

Studio Build:
Android Studio 3.6 Canary 6
Build #AI-192.5587.17.36.5787298, built on August 7, 2019
Runtime version: 1.8.0_202-release-1483-b49-5587405 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: ParNew, ConcurrentMarkSweep
Memory: 1979M
Cores: 16
Registry: testDiscovery.enabled=true, ide.mac.new.color.picker=true, search.everywhere.structure=true, terminal.buffer.max.lines.count=, idea.true.smooth.scrolling.interpolation=true, ide.new.welcome.screen.force=true, search.everywhere.settings=true, ide.mac.allowDarkWindowDecorations=true, debugger.watches.in.variables=false, projectView.choose.directory.on.compacted.middle.packages=true, show.affected.tests.in.changelists=true, terminal.persistent.tabs=false, terminal.distraction.free=true, cidr.max.intellisense.file.length=1000000
Non-Bundled Plugins: com.zxy.idea.plugin.external-plugin-support

Steps to Reproduce:
1. create a new android project
2. add a new java library module
3. configure the java library module with `apply plugin: 'java-test-fixtures'`
4. add some dependencies to the `testFixturesApi` configuration, ie: testFixturesApi("junit:junit:4.12")
5. sync project with studio
6. attempt to write source inside the testFixtures src set
7. dependencies added to testFixturesApi are not available for code completion or indexed (imports and usages in red)

https://docs.gradle.org/5.6/release-notes.html#test-fixtures-for-java-projects

Comments

vi...@google.com <vi...@google.com> #2Aug 22, 2019 06:03AM

Assigned to tn...@google.com.

Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.

tn...@google.com <tn...@google.com> Aug 30, 2019 03:47PM

Reassigned to xa...@google.com.

xa...@google.com <xa...@google.com> #3Aug 30, 2019 04:29PM

Reassigned to so...@google.com.

We need to investigate this. This is a new feature of gradle that generate a new source set that we have to import.
We currently use an older mechanism to import Java project (main/test in the same IntelliJ module using IJ's main/test sourcesets), but this does not work for new source sets. IJ is now creating a separate module per source sets and we need to move toward this in order to support this.

However this cannot happen in 3.6 as we are too close to beta, so it's going to have to wait until 3.7.

xa...@google.com <xa...@google.com> #4Aug 30, 2019 04:30PM

Yuriy, can you at least try it and see what's going on? we should probably document this limitation at least.

xa...@google.com <xa...@google.com> #5Aug 30, 2019 09:49PM

Reassigned to sm...@google.com.

Moving this to Bradley after we discuss this as it's tied to moving back to IJ's handling of Java project.

ai...@gmail.com <ai...@gmail.com> #6Jan 26, 2020 10:43AM

Any progress on this?
It's extremely useful feature for multi-module projects to share test-related utilities, now we have to copy-paste module-specitic test utilities, stubs, fakes etc. Extract it to own test module is also an option, but requires much more boilerplate and not free for configuration time.

ro...@gmail.com <ro...@gmail.com> #7Feb 11, 2020 08:11PM

Any updates? Since this whould be very usefull when modularizing

sm...@google.com <sm...@google.com> #8Feb 11, 2020 08:23PM

It's being worked on, unfortunately there is a lot of internal cleanup that needs to happen first. I'll keep this bug updated.

uc...@google.com <uc...@google.com> Feb 13, 2020 11:53PM

Reassigned to an...@google.com.

se...@gmail.com <se...@gmail.com> #9Feb 21, 2020 12:52AM

Workaround to fix Gradle sync:

android.injected.restrict.variant.name=false

xa...@google.com <xa...@google.com> #10Feb 25, 2020 01:13AM

Reassigned to sm...@google.com.

do not use `

android.injected.restrict.variant.name`. This is actually gone from 4.1 as it was for the old, no deprecated/removed, Instant Run.

ro...@miquido.com <ro...@miquido.com> #11Mar 5, 2020 01:03PM

What about android library module. Any progress or plans to support testFixtures also for android libraries?

xa...@google.com <xa...@google.com> #12Mar 9, 2020 04:03PM

we are making progress toward this yes.

se...@gmail.com <se...@gmail.com> #13Oct 15, 2020 09:18AM

Well, AGP 7.0 will surely be exciting.

l....@gmail.com <l....@gmail.com> #14Oct 16, 2020 10:19AM

Can you share some more details here? "Blocking Release -> AGP-7.0 Beta" looks either like a mistake or something related to planning not known to the general public. Should we expect this feature in ~3 years (at least) from now, when AS 7 will be released?

Message last modified on Oct 16, 2020 10:19AM

xa...@google.com <xa...@google.com> #15Oct 16, 2020 06:09PM

AGP 7.0 is the version after 4.2. We'll announce more about it when the first canary lands (once 4.2 moves into beta).

lo...@gmail.com <lo...@gmail.com> #16Oct 16, 2020 09:24PM

Is that decoupling of AGP and Android Studio releases? Anyway, staying tuned, looking forward the blog post.

tr...@gmail.com <tr...@gmail.com> #17Oct 21, 2020 01:58AM

given that this was blocked by migrating to the newer way gradle and intellij interact. and that if we look at https://github.com/gradle/gradle/milestones currently showing the next two milestones as 6.8 & 7.0. a paradigm shift in versioning to follow that of the tool that AGP directly integrates/coexists with seems like a fairly safe bet. Though given the nature of any intelligent and integrated tool chain I can't imagine that AGP will be any less coupled to the the IDE version unless they have reinvented the communication medium of AGP and Studio to be more dynamic. Not entirely impossible given recent changes in the core idea platform being able to configure and reload plugins without a restart. (given the plugins are implemented to support it?)

Maybe a future where [android studio](skinned intellij IDEA with a smarter plugin system) dynamically adjusts to the project's configuration is a reality without undue maintenance burden on both teams.

eu...@gmail.com <eu...@gmail.com> #18Jul 23, 2021 09:50AM

Was it already announced or documented publicly?

xa...@google.com <xa...@google.com> #19Jul 23, 2021 05:43PM

It's not yet supported.

sm...@google.com <sm...@google.com> #20Feb 1, 2022 04:35AM

Marked as fixed.

Thanks for the bug report, this should be working on newer versions of the chipmunk canaries. Please let us know if this is not the case.

tr...@gmail.com <tr...@gmail.com> #21Feb 2, 2022 12:02AM

Just confirmed. it is behaving well in chipmunk beta 1. Including when the project is still on AGP 7.1.0

Thanks all