From e450569a698d796940f94ef1364039fcf208c01a Mon Sep 17 00:00:00 2001 From: Hans-Christoph Steiner Date: Thu, 16 Aug 2018 15:03:02 +0200 Subject: [PATCH] espresso: do extra memory clean up to keep StrictMode happy There were some occasional StrictMode errors about multiple instances of MainActivity. This cleanup idea comes from Google: https://github.com/aosp-mirror/platform_frameworks_base/commit/6f3a38f3afd79ed6dddcef5c83cb442d6749e2ff --- .../org/fdroid/fdroid/MainActivityEspressoTest.java | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/app/src/androidTest/java/org/fdroid/fdroid/MainActivityEspressoTest.java b/app/src/androidTest/java/org/fdroid/fdroid/MainActivityEspressoTest.java index 7fd5a57b9..cab19db4a 100644 --- a/app/src/androidTest/java/org/fdroid/fdroid/MainActivityEspressoTest.java +++ b/app/src/androidTest/java/org/fdroid/fdroid/MainActivityEspressoTest.java @@ -17,6 +17,7 @@ import android.view.View; import org.fdroid.fdroid.views.BannerUpdatingRepos; import org.fdroid.fdroid.views.main.MainActivity; import org.hamcrest.Matchers; +import org.junit.After; import org.junit.AfterClass; import org.junit.BeforeClass; import org.junit.Rule; @@ -101,6 +102,18 @@ public class MainActivityEspressoTest { || "google_sdk".equals(Build.PRODUCT); } + /** + * Placate {@link android.os.StrictMode} + * + * @see Run finalizers before counting for StrictMode + */ + @After + public void tearDown() { + System.gc(); + System.runFinalization(); + System.gc(); + } + @Rule public ActivityTestRule activityTestRule = new ActivityTestRule<>(MainActivity.class);