Files
AndroidDeviceStreaming/docs/verification.md
T

2.0 KiB

Verification record

Validated on Windows x64 during implementation:

  • go test ./...: role authentication, offline devices, duplicate registration, exclusive leases, ticket ownership and replay rejection, bidirectional bytes, stream cancellation, agent disconnect cleanup.
  • go vet ./...: passed.
  • cargo test --workspace --locked: configuration validation and ADB smart socket handshake with fragmented replies.
  • cargo clippy --workspace --all-targets --locked -- -D warnings: passed.
  • Release builds: Go relay and both Rust executables built successfully.
  • python tests/e2e.py against the release binaries: passed 2 MiB binary transfer, eight concurrent streams, an idle stream across control ping/pong, competing-client rejection, agent restart and relay restart recovery.
  • Existing Python bridge unit tests: all three passed.

Read-only real-device smoke test:

  • Remote ADB Server 192.168.5.222:5037 listed 192.168.100.141:5555 as online.
  • Started a temporary relay and both Rust daemons, with the gateway using the existing remote ADB transport.
  • Initial attempt reached the phone but returned unauthorized. After the user approved the local computer's key, the same test was rerun successfully.
  • Ordinary local adb devices -l listed 127.0.0.1:51847 as device, with product aosp_crosshatch and model AOSP_on_crosshatch.
  • Remote adb shell getprop ro.product.model returned AOSP on crosshatch; the read-only shell echo marker also matched. All three release programs were involved in the successful test.
  • App installation, Android Studio and scrcpy have not yet been exercised through the new path.
  • Temporary processes and local ADB endpoint were disconnected after the test; unrelated local ADB devices were preserved.

No public server was deployed. Production WSS certificates, real Internet latency, and Linux/macOS runtime behavior still need deployment-environment validation. The Linux Go server is cross-built separately; cross-building is not a Linux runtime test.