From 52a8a07172d5a359d01fbb40262e7ce6d99bd334 Mon Sep 17 00:00:00 2001 From: Googler Date: Tue, 22 Mar 2022 12:07:13 -0700 Subject: [PATCH] Correctly register all idling resources This was a test bug that caused this test to flake because the idling resources were not waiting for resource "C" to become idle. PiperOrigin-RevId: 436558912 --- .../integrationtests/axt/EspressoIdlingResourceTest.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration_tests/androidx_test/src/test/java/org/robolectric/integrationtests/axt/EspressoIdlingResourceTest.java b/integration_tests/androidx_test/src/test/java/org/robolectric/integrationtests/axt/EspressoIdlingResourceTest.java index 36565a24a75..f70c0c95287 100644 --- a/integration_tests/androidx_test/src/test/java/org/robolectric/integrationtests/axt/EspressoIdlingResourceTest.java +++ b/integration_tests/androidx_test/src/test/java/org/robolectric/integrationtests/axt/EspressoIdlingResourceTest.java @@ -88,7 +88,7 @@ public void onIdle_cooperativeResources() { NamedIdleResource a = new NamedIdleResource("A", /* isIdle= */ true); NamedIdleResource b = new NamedIdleResource("B", /* isIdle= */ false); NamedIdleResource c = new NamedIdleResource("C", /* isIdle= */ false); - idlingRegistry.register(a, b); + idlingRegistry.register(a, b, c); executor.submit( () -> { a.setIdle(false);