From 66a28d5abb5a4db604a95d0183ac6923d5e73faf Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Tue, 4 Aug 2026 18:14:13 +0200 Subject: [PATCH] ci(android): run the kit's unit tests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit They were running nowhere. This workflow only assembled, and the screenshot workflow runs the :app module's tests, so nothing enforced :kit's — the pure parsers, migrations and feedback policies could go red without anyone noticing. A couple of seconds against a module the build already produces. --- .gitea/workflows/android.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.gitea/workflows/android.yml b/.gitea/workflows/android.yml index 87635c67..43fe3cb9 100644 --- a/.gitea/workflows/android.yml +++ b/.gitea/workflows/android.yml @@ -160,6 +160,14 @@ jobs: key: gradle-${{ hashFiles('clients/android/**/*.gradle.kts', 'clients/android/gradle/wrapper/gradle-wrapper.properties') }} restore-keys: gradle- + # The kit's JVM unit tests — the pure parsers, migrations and feedback policies. They were + # running nowhere: this workflow only assembled, and android-screenshots.yml runs the :app + # module's tests, so nothing enforced :kit's. Cheap (a couple of seconds against an already + # built module) and it is the only automated cover those behaviours have. + - name: kit unit tests + working-directory: clients/android + run: ./gradlew :kit:testDebugUnitTest --stacktrace + - name: assembleDebug (cargo-ndk → jniLibs → APK) working-directory: clients/android env: