20

My Espresso tests were running until I had to support multidex.

My build.gradle, I have

minSdkVersion 14
targetSdkVersion 23
multiDexEnabled = true

testInstrumentationRunner "com.android.test.runner.MultiDexTestRunner"


androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.1'
androidTestCompile 'com.android.support.test.espresso:espresso-contrib:2.2.1'
androidTestCompile 'com.android.support.test:runner:0.4.1'
androidTestCompile 'com.android.support.test:rules:0.4.1'

dexOptions {
        jumboMode true
        javaMaxHeapSize "4g"
        incremental true
    }

Test1AuthenticationEspressoTest

@RunWith(AndroidJUnit4.class)
@SmallTest
public class Test1AuthenticationEspressoTest {
    @Rule
    public ActivityTestRule<WelcomeActivity> mActivityRule = new  ActivityTestRule(WelcomeActivity.class);

}

Here is the Error I get

junit.framework.AssertionFailedError: No tests found in com.livestrong.tracker.test.Test1AuthenticationEspressoTest

Any help will be appreciated. Any one has espresso working with multidex ?

Sayooj Valsan
  • 536
  • 5
  • 16

1 Answers1

41

I was having this same problem and it turns out you need to build a custom runner that enables MultiDex and extends from the AndroidJUnitRunner. You then need to set that runner as your testInstrumentationRunner in the build.gradle, and as your runner in your run configuration. There is no need to modify the test class (keep the @RunWith(AndroidJunit4.class)).

Here's a step-by-step of what to do:

  1. Create a class for your custom runner:

    package com.bla.bla.bla;  // your package

import android.os.Bundle;
import android.support.multidex.MultiDex;
import android.support.test.runner.AndroidJUnitRunner;

public class CustomTestRunner extends AndroidJUnitRunner
{
    @Override
    public void onCreate(Bundle arguments)
    {
        MultiDex.install(getTargetContext());
        super.onCreate(arguments);
    }
}

  2. In your build.gradle, set the runner to your custom runner:

    android {
    // ...
    defaultConfig {
        // ...
        testInstrumentationRunner "com.bla.bla.bla.CustomTestRunner"
    }
}

  3. In your run configuration, make sure the instrumentation runner is also set to the same runner.. Note: This step should not be required on Android Studio 3.x and maybe also some previous versions. This option does not exist anymore.

Using the above, I was able to run Espresso tests on our multi-dex enabled app.

I should note that many other posts on the net regarding this topic, suggest setting your runner to com.android.test.runner.MultiDexTestRunner and exculde some dependencies in com.android.support:multidex-instrumentation:1.0.1 in your build.gradle. That solution appears to no longer be the case and doesn't work as of gradle 1.5.0. If you have any of that stuff set, then it'll prevent the above from working. See the comments in this stack overflow post for more information.

k_o_
  • 5,143
  • 1
  • 34
  • 43
Billy
  • 547
  • 3
  • 5
  • 4
    Your answer were promissing, but I still get an issue : Error:Execution failed for task ':app:transformClassesWithMultidexlistForDebugAndroidTest'. > com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1 – Anthony Feb 11 '16 at 10:09
  • 2
    This answer should be ACCEPTED. – Elye Jun 30 '16 at 05:53
  • This is basically working for me, except for one thing: when I run this way any of my code that references classes in jars pulled in from the 'libs' directory (loaded like so `compile fileTree(dir: 'libs', include: '*.jar')`) will fail with `NoClassDefFoundError`. Everything else works fine. – David Pisoni Sep 22 '16 at 22:18
  • 1
    This doesn't work. In addition, your code is exactly what's in MultiDexTestRunner, so if this code did work it wouldn't be necessary. – Gabe Sechan Sep 13 '17 at 18:21