Files
AndroidDeviceStreaming/docs/verification.md
T

1.7 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.
  • Local adb connect reached the phone through the new three-program path, but Android returned unauthorized for the local computer's key.
  • Consequently, real adb shell, app installation, Android Studio and scrcpy have not been verified through the new path. Approve the local key on the phone, then rerun tests/real_device.py.
  • 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.