Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Method setUp in android.test.AndroidTestCase not mocked

I'm trying to come to terms with the new unit test feature of Android Studio. I've followed the instructions on http://tools.android.com/tech-docs/unit-testing-support. The description there explicitly mentions the 'Method ... not mocked' error and suggests to put the following into the build.gradle:

android {
  // ...
  testOptions { 
    unitTests.returnDefaultValues = true
  }
}

This works in so far as the tests run when started from the command line with

gradlew test --continue

but not when I run the test class from Android Studio with rightclick -> run. This way, I get the same error again:

java.lang.RuntimeException: Method setUp in android.test.AndroidTestCase not mocked. See https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support for details.
    at android.test.AndroidTestCase.setUp(AndroidTestCase.java)
    at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
    at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
    at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
    at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)

Any ideas on how to solve this?

EDIT: The content of the test class doesn't really matter because the setUp of the test fails, I tried with the most simple class:

public class ContactFormToolTest extends AndroidTestCase {    

    public void testSOmething(){
        assertEquals(false, true);
    }            
}

Also tried overriding setUp, makes no difference.

like image 617
fweigl Avatar asked Feb 27 '15 09:02

fweigl


2 Answers

From: https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support#TOC-Method-...-not-mocked.-

The android.jar file that is used to run unit tests does not contain any actual code - that is provided by the Android system image on real devices. Instead, all methods throw exceptions (by default). This is to make sure your unit tests only test your code and do not depend on any particular behaviour of the Android platform (that you have not explicitly mocked e.g. using Mockito). If that proves problematic, you can add the snippet below to your build.gradle to change this behavior:

android {

   // ...   

  testOptions { 
      unitTests.returnDefaultValues = true   
  } 
}
like image 169
Oded Regev Avatar answered Oct 30 '22 22:10

Oded Regev


The new Unit Tests feature in Android Studio fakes the entire Android SDK so that you can run fast, Java-only tests, without needing to install your application on an Android device (this is similar to Robolectric). The general idea is that you mock all the responses from the Android SDK calls.

AndroidTestCase is used to run a test with the real Android SDK.

So, your issue is that you are trying to run an AndroidTestCase that depends on the Android SDK, but your test runner is launching the Unit Tests environment, which uses a fake Android SDK instead of a real one.

You need to choose one approach. If you want a pure unit test, then you probably should use a JUnit 4 test class instead of an AndroidTestCase. More instructions here: https://developer.android.com/training/testing/unit-testing/local-unit-tests.html#build

like image 24
Dan J Avatar answered Oct 30 '22 22:10

Dan J