Modularised Android testing - module test using base module test

Question

I have a android project with multiple modules, module B that depends on module A

dependencies {
    implementation project(':features:A')
}

I want unit test in module B to extend base test from module A. An IDE resolved all dependencies successfully, but in build time only production code from module A is accessable in test.

I tried to add dependency specificly for tests:

dependencies {
    testCompile project(':features:A').sourceSets.test.output
}

This results an error:

Could not get unknown property 'test' for SourceSet container of type org.gradle.api.internal.tasks.DefaultSourceSetContainer.

Same if I'm trying to create custom artifact with tests.

How can I get access to test-specific code in base module from dependent module?

AS 3.1, gradle 4.1

DmitryBorodin · Accepted Answer · 2018-03-28 12:55:05Z

1

The best solution I found is to create third module just for tests, put my base test classes and test dependencies there. And use it in both module A and module B (and all other modules - just one module for all unit test dependencies)

testImplementation project(':features:basetests')

Disadvantage - it is possible to import it in non-test artifacts (e.q. implementation project(':features:basetests')). Good code review can protect from such mistakes. Looks like there is no convenient way to define base shared test-only code.

answered Mar 28, 2018 at 12:55

DmitryBorodin

5,0225 gold badges21 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Modularised Android testing - module test using base module test

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related