27

I want to achieve something like this:

[ComponentTestsModule] com.android.test
[FunctionalTestsModule] com.android.test
both depends on
 -> [TestLibraryModule] ?
which depends on
   -> [AppModule] com.android.application

Is there any way to do it with android Gradle plugin 3.0+?

Why I need multiple test modules?

I want different test runners for different types of tests, also target different variants. It is working right now with single codebase under androidTest, but with ugly switches in the custom test runner.

Why I need a test library module?

I want to share the same page-objects between different types of tests, and maybe some utility code. Problem is: that page objects must have access to R class of app (locators: R.id.*)

None of the module types I'm aware of can depend on APK-producing module, expect from com.android.test, but i cannot depend from com.android.test with another com.android.test.

Shehan Dhaleesha
  • 627
  • 1
  • 10
  • 30
Dmitriy Voronin
  • 649
  • 6
  • 19

2 Answers2

8

I have recently faced this problem and just want to share my solution in case some body needs it.

What I have done so far (not a perfect solution - I guess, but at least it works).

  1. Create a new module named testing_base or some thing like that

  2. In testing_base module only put things related to testing (Like the code you want it to be shared between modules) in to normal packages, NOT in the test packages/folders.

  3. From others module, try to import things from testing_base module

ex: testImplementation project(":testing_base")

Hope it can helps someone, happy testing!

ThaiPD
  • 3,503
  • 3
  • 30
  • 48
  • d= (◕‿↼ ) Thanks! Unfortunately, creating a new library is the only way to separate test-code from regular-code. – Top-Master May 26 '22 at 04:40
  • when run code from command line i got error ` Project with path ':mylibrary' could not be found in project ` – Mahmoud Mabrok Jan 22 '23 at 12:25
  • @MahmoudMabrok you probably setting up the new module in a wrong way. – ThaiPD Jan 23 '23 at 09:39
  • this error occured only when i use the module that have `mylibrary` at another module. like Module 1 have module 2, so when i use Module 1 at module 3 i got that error. – Mahmoud Mabrok Jan 23 '23 at 12:55
  • Let's say you have `module1`, `module2` and `module3`. `Module1` has dependency to `module2` and `module3` has dependency to `module1`. So which module has dependency to `mylibrary` ? – ThaiPD Jan 23 '23 at 13:22
-3

I want different test runners for different types of tests

To run a test class with a specific test runner, use the @RunWith annotation.

also target different variants

To target a specific variant, create your tests in app/src/androidTestVariantName for instrumented tests or in app/src/testVariantName for unit tests.

Code-Apprentice
  • 81,660
  • 23
  • 145
  • 268