Test, Package and Release Phone-Built Projects
Move from “it runs once” to repeatable tests, documented dependencies, versioned archives and automated checks.
Move from “it runs once” to repeatable tests, documented dependencies, versioned archives and automated checks.
Core ideas
- Write a smoke test for startup, one expected success and one expected failure.
- Pin or document dependency versions and produce a checksum for release archives.
- Use GitHub Actions for validation while keeping the project runnable locally in Termux.
Decision rule
Do not publish a release until a fresh clone can reproduce the documented setup.
Apply it on your phone
Create a release checklist that builds, tests, hashes and archives a project without manual file selection.