budget-app/docs/CAPTURE_VALIDATION.md

25 lines
2.7 KiB
Markdown

> Historical revision record. For the current Cargo-only pipeline and test locations, see Readme, TESTING.md and GRADLE_FREE_VALIDATION.md.
# Floating-capture validation — original implementation, 26 October 2026
Historical results before the workspace refactor. See `WORKSPACE_ARCHITECTURE.md` and the workspace validation report for the current architecture/checks.
## Executed successfully
- Android app Java compilation and test-only harness APK assembly (AGP 8.7.3, Gradle 8.9, JDK 17, SDK 35).
- 12 `ProductExtractionTest` cases: 0 failures, 0 errors.
- APK manifest inspection: no `android.permission.INTERNET`; only the capture/foreground/notification permissions and AndroidX's private receiver permission were present.
- APK inspection: bundled ML Kit OCR native libraries and on-device model assets were present.
- Integrated manifest/resource processing and Java compilation using the actual Makepad Java sources at `2d732a5aa1e7648b1d5751140f5842ac99b03f79` plus Budget's app Java and capture classes.
- 3 Python packaging tests: private capture components, system-protected tile, offline manifest, preserving native activity package, staging assets/native libraries, and rejecting unexpected secondary DEX files.
- Existing Makepad app-Java-hook detection tested: helper exits successfully without changing the packager source.
- Bash syntax, Python syntax and Git whitespace checks passed.
- Temporary JDK, SDK, Gradle, caches, copied sources and outputs were removed after the final run. Earlier failed validation attempts also cleaned up. The initial integrated-Java source download was rejected by the website's raw-commit route; it was replaced by the public immutable-revision contents API with Git blob hash verification, then rerun successfully.
## What this does NOT establish
The harness APK is test-only, contains no Rust Budget engine, and is not a deliverable application. The integrated Java compile fixture deliberately uses a dummy native payload and is never assembled/distributed. No claim is made that the final native APK was installed or that MediaProjection, overlay placement/keyboard behavior, OCR accuracy, Android lifecycle transitions or financial-data persistence were tested on a physical device/emulator.
The Rust/native desktop app was validated earlier in this session (95 tests, full build/link, 15-second Linux launch smoke test). This Android feature changes no Rust source, but that earlier test is not validation of these new Android runtime paths.
Before release, build/sign the real integrated APK and run the device matrix in `ANDROID_CAPTURE.md`. In particular test API 34/35 consent and service lifecycles, protected surfaces, stopped/revoked captures, repeated captures, rotation, edits/discard/confirmation and data-preserving upgrades.