This works: testCompile project (path: ‘:A’, configuration: ‘testArtifacts’)
This fails: testImplementation project (path: ‘:A’, configuration: ‘testArtifacts’)
I don’t want to completely restructure the project using the new “fixtures”. However, I’d like to migrate to the api/implementation configurations instead of using compile/testCompile for managing dependencies.
What is the preferred way to include a module’s test classes as a dependency for another module?
I tried this solution, it didn’t work for me. I have a large android app, that contains many modules, I have the same exact issue as described. the project has no project group or groupid, if I try this solution gradle throws an error saying that the format is groupid:artificat:version, how could I solve this?