From ee791b181ce80681bd93d0f2f07b73f2716c57e3 Mon Sep 17 00:00:00 2001 From: Gregor MacLennan Date: Thu, 2 Jul 2026 06:01:32 +0100 Subject: [PATCH] fix(scripts): fail the unit-test runner when the Gradle test task fails run_unit_tests swallowed any failure of :comapeo-core-react-native:test with a "module name may differ" warning, so --unit-only exited 0 even on a Kotlin compile error and stale test-results XML read as a pass. The module name is fixed by Expo autolinking in this repo, so the guard protects nothing; with set -e in effect, the bare invocation now aborts the run with a non-zero exit. --- scripts/run-instrumented-tests.sh | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/scripts/run-instrumented-tests.sh b/scripts/run-instrumented-tests.sh index 621514d1..b769329c 100755 --- a/scripts/run-instrumented-tests.sh +++ b/scripts/run-instrumented-tests.sh @@ -92,10 +92,7 @@ run_unit_tests() { echo "" echo "==> Running JVM unit tests..." cd "$EXAMPLE_DIR/android" - # The library module name in the Gradle build varies by Expo setup. - # Run via the app module which includes the library. - ./gradlew :comapeo-core-react-native:test || \ - echo "Warning: Library module test task failed. This may be expected if the module name differs." + ./gradlew :comapeo-core-react-native:test cd "$PROJECT_ROOT" }