AndroidJUnitRunner跳过了Android Junit4测试，ProviderTestCase2在tearDown（）中生成NullPointerException

我想获得一些帮助，确定如何跳过我的

@Test

。我会解释我在解决这个问题上经历了什么。使用下面包含的测试，测试运行程序点击

setUp（）

和

tearDown（）

，但不点击注释为

@test

的测试，如下所示为

testandroidTestCaseSetupRightly

测试的“运行/调试配置”“特定检测运行程序”设置设置为

android.support.test.runner.AndroidJUnitRunner

我已经构建了以下测试，以针对StorageProvider示例应用程序运行，该应用程序是通过AndroidStudio 1.5.1中的

File->New->Import sample

提供的，带有gradle插件版本1.5.0。我相信我已经按照中的说明构建了测试

@RunWith(AndroidJUnit4.class)
public class MyCloudProviderTest extends ProviderTestCase2 {
    private static final String AUTHORITY = "com.example.android.storageprovider.documents";
    private static final String FILENAME = "foo";
    private static final String LOGTAG = "MCPT";
    private File mFile;

    public MyCloudProviderTest() {
        super(MyCloudProvider.class, AUTHORITY);
    }

    @Override
    @Before
    public void setUp() throws Exception {
        Log.v(LOGTAG, "Setting Up MyCloudProviderTest");
        setContext(InstrumentationRegistry.getTargetContext());
        super.setUp();
        super.testAndroidTestCaseSetupProperly();
        mFile = new File(getMockContext().getFilesDir().getPath(), FILENAME);
        if (!mFile.exists()) {
            mFile.createNewFile();
        }
    }

    @Override
    @Test
    public void testAndroidTestCaseSetupProperly() {
        Log.v(LOGTAG, "testing AndroidTestCaseSetupProperly");
        super.testAndroidTestCaseSetupProperly();
        assertTrue(mFile.exists());
        assertNotNull(getProvider());
    }

    @Override
    @After
    public void tearDown() throws Exception {
        Log.v(LOGTAG, "Tearing Down MyCloudProviderTest");
        super.tearDown();
    }
}

在我的模块build.gradle中，我包括了如下所示的依赖项，以及

android->defaultConfig->testInstrumentationRunner“android.support.test.runner.AndroidJUnitRunner”下的配置，如
此处包含模块的build.gradle

apply plugin: 'com.android.application'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.2"

    defaultConfig {
        minSdkVersion 19
        targetSdkVersion 22
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_7
        targetCompatibility JavaVersion.VERSION_1_7
    }
}

dependencies {
    androidTestCompile 'com.android.support:support-annotations:23.1.1'
    androidTestCompile 'com.android.support.test:runner:0.4.1'
    androidTestCompile 'com.android.support.test:rules:0.4.1'

    compile 'com.android.support:support-v4:23.1.1'

    compile 'junit:junit:4.12'
    testCompile 'junit:junit:4.12'
}

gradle中的projections build.gradle包括

dependencies {
    classpath 'com.android.tools.build:gradle:1.5.0'
}

在运行这些测试时，我可以通过在
@Test
注释中放置断点或读取logcat来确认注释是否被跳过，其内容如下（注意缺少“testing AndroidTestCaseSetupRightly”）：

我已经进行了广泛的搜索，寻找一些东西来澄清为什么跳过@Test注释的方法，但是我所看到的案例似乎不适用于
JUnit4
测试
ProviderTestCase2

除此之外，跳过
@Test
方法，代码还抛出以下堆栈跟踪。我将这些问题结合在一起，因为它们几乎肯定是相关的，事实上可能会相互启发：

Running tests
Test running started
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.content.ContentProvider.shutdown()' on a null object reference
at android.test.ProviderTestCase2.tearDown(ProviderTestCase2.java:167)
at com.example.android.storageprovider.MyCloudProviderTest.tearDown(MyCloudProviderTest.java:47)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)
at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:240)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)

你找到答案了吗？
Running tests
Test running started
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.content.ContentProvider.shutdown()' on a null object reference
at android.test.ProviderTestCase2.tearDown(ProviderTestCase2.java:167)
at com.example.android.storageprovider.MyCloudProviderTest.tearDown(MyCloudProviderTest.java:47)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)
at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:240)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)