android-test-apps
| Version | 2026.145.1700 |
| Repo | box/github.com/opencharly/layer-android-test-apps:v2026.251.0811 |
Android apps installed onto a kind: android device via the apk:
package format — the declarative counterpart to the charly check adb install-app probe verb. Carries the F-Droid client (org.fdroid.fdroid)
as a COMMITTED APK (tests/data/F-Droid.apk — the canonical client from
f-droid.org, NOT an apkeep download), pushed over the goadb sync
protocol. A target: android deploy applies this layer’s apk: list
onto the running device through the external deploy:android substrate
(candy/plugin-adb installFromHostApk: pure goadb push + pm install — no
apkeep, no source: — venue-agnostic for the in-pod image device AND a
remote endpoint). Pair with the android-apidemos layer (the same
committed-APK path) so both fixture anchors share one acquisition story.
The candy installs NOTHING into the image — the apk: list is
device-scoped, applied ONLY by a target: android deploy (skipped at
image build and on every other target). Its observable effect is
therefore on the running device: after the deploy, pm list packages
reports org.fdroid.fdroid and the app launches, so the install is
verifiable end to end over goadb (adb).
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
F-Droid (org.fdroid.fdroid) is installed on the device after a target:android deploy |
check |
the installed F-Droid launches and its process is running |