Fix FlutterInjectorTest assumptions about how the executor service assigns tasks to threads (flutter#44775)

jason-simmons · web-flow · commit 4f967f33d7c6 · 2023-08-17T20:37:59.000Z
diff --git a/shell/platform/android/test/io/flutter/FlutterInjectorTest.java b/shell/platform/android/test/io/flutter/FlutterInjectorTest.java
@@ -8,6 +8,7 @@
 import static org.junit.Assert.assertNotNull;
 import static org.junit.Assert.assertNull;
 import static org.junit.Assert.assertThrows;
+import static org.junit.Assert.assertTrue;
 
 import androidx.test.ext.junit.runners.AndroidJUnit4;
 import io.flutter.embedding.engine.deferredcomponents.PlayStoreDeferredComponentManager;
@@ -73,8 +74,9 @@ public void executorCreatesAndNamesNewThreadsByDefault()
     threadNames = injector.executorService().invokeAll(callables);
 
     assertEquals(threadNames.size(), 2);
-    assertEquals(threadNames.get(0).get(), "flutter-worker-0");
-    assertEquals(threadNames.get(1).get(), "flutter-worker-1");
+    for (Future<String> name : threadNames) {
+      assertTrue(name.get().startsWith("flutter-worker-"));
+    }
   }
 
   @Test
