mirror of
https://github.com/priyanshujain/sanderling.git
synced 2026-10-02 11:07:10 +00:00
* fix(runner): warn on malformed screen snapshot screenFromSnapshot swallowed json.Unmarshal errors, so a non-string screen value silently became "" in the step log and trace while the verifier still saw the raw JSON. Return the error and warn at the call site, matching the hierarchy warning pattern. * docs: clarify --avd is optional for uatu test The CLI accepts --avd as an empty-string default (cmd/uatu/main.go:49) and only requires it when no device is connected and multiple AVDs exist (cmd/uatu/android_env.go:63). Docs and examples that showed it as required or always-passed were misleading.
1.4 KiB
1.4 KiB
uatu sample app
Tiny Android app wired to the uatu SDK, plus a TypeScript spec that drives it. Use it as a reference for integrating uatu into your own app.
Prerequisites
uatuCLI onPATH(see getting started)- Android SDK installed (uatu auto-discovers
adbandemulatorunder$ANDROID_HOME,~/Library/Android/sdk, or the Homebrew cask; nothing to export if you use a standard install) justtask runner
Install the app
just install
Run a test
just test
If no device is connected, uatu boots the single AVD it finds. With multiple AVDs, pick one:
just AVD=Pixel_7 test
Persistent settings can live in .env alongside the justfile:
AVD=Pixel_7
DURATION=5m
Traces land in ./runs/<timestamp>/.
How the pieces connect
android/build.gradle.ktsdepends onio.github.priyanshujain:sdk-androidfrom Maven Centralandroid/src/main/kotlin/.../SampleApplication.ktcallsUatu.start(this)and registers snapshot extractors (app_state,click_count)spec.tsimports@uatu/spec(seepackage.json), reads those snapshots, asserts properties on them, and weights the actions the fuzzer picks fromjust testinvokesuatu testagainst the installed APK on the connected device (or the AVD named viaAVD=)