Skip to content
OpenCharly

android-test-apps

Recipe card from the charly-check plugin (Commands — runtime CLI verbs).

android-test-apps — Android fixture apps via the apk: format

Section titled “android-test-apps — Android fixture apps via the apk: format”

Candy Properties

Section titled “Candy Properties”
Property Value
Installs into image nothing (device-scoped)
apk: list tests/data/F-Droid.apk (committed)
Applied by a target: android deploy (skipped at image build)
Verified by adb: pm list packages / pidof after the deploy

What it does

Section titled “What it does”

Carries the F-Droid client (org.fdroid.fdroid) as a committed APK (tests/data/F-Droid.apk), pushed over the goadb sync protocol and installed with pm install. It is the declarative counterpart to the charly check adb install-app verb. The candy installs nothing into the image — the apk: list is device-scoped and applied ONLY by a target: android deploy (via the external deploy:android substrate, venue-agnostic for an in-pod image device or a remote endpoint).

Usage

Section titled “Usage”

Compose it in the box that backs a kind: android deploy:

android-fixtures:
  candy:
    base: cachyos-base
    candy:
      - '@github.com/opencharly/layer-android-test-apps:v2026.xxx.yyyy'
      - '@github.com/opencharly/layer-android-apidemos:v2026.xxx.yyyy'

Verification

Section titled “Verification”

The plan: check: steps run at context: [runtime] after a target: android deploy: pm list packages must contain org.fdroid.fdroid, and launching it (monkey … LAUNCHER) must yield a running PID — proving the install end to end over adb.

Section titled “Related”