Files
AndroidDeviceStreaming/docs/verification.md
T

56 lines
6.2 KiB
Markdown

# 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.
Public deployment follow-up:
- Linux amd64 server is now running on Debian 12 at `175.178.213.60`, as an enabled systemd service under a dedicated user.
- Existing Nginx proxies `https://ttstd.com/ads/` to loopback `127.0.0.1:18081`, stripping the prefix. Its existing root-domain certificate was verified without disabling certificate checks.
- A real public WSS smoke test passed: both Rust daemons connected to the public origin while keeping TLS SNI/hostname `ttstd.com`; ordinary local ADB listed `127.0.0.1:59671` as `device`, and both read-only shell commands passed.
- The initial public test used a temporary local gateway and the VPN-reachable remote ADB Server. Follow-up deployment now runs the actual gateway on the remote Windows PC; see the next section.
- Public Cloudflare DNS connectivity timed out from the current PC; the explicit origin-address option was used. No DNS records were changed.
- macOS runtime and Linux Rust daemon hosting remain untested. See `deployment-ttstd.md` for deployed configuration and certificate expiry.
Remote Windows gateway follow-up:
- Installed release `ads-agent.exe` on `192.168.5.222`, under `C:\Users\TT\AppData\Local\AndroidDeviceStreaming\agent`. Remote SHA256 matched the local release artifact.
- Created an ACL-protected credential directory and registered `ADS-Agent` as a hidden background task under `TT`, with password logon, startup/logon triggers and failure restart. No account password is written into source or deployment files.
- The gateway directly connects to phone `192.168.100.141:5555` and public relay origin `175.178.213.60:443`, retaining hostname `ttstd.com` and normal TLS checks.
- Ran `tests/real_device.py --existing-device home-phone`: only a local client was started; no local gateway and no remote ADB Server transport were used. Ordinary local ADB showed the phone as `device`, and model query plus shell marker passed.
- Restarted the remote task and repeated that test: passed again, with local endpoint `127.0.0.1:49832` and model `AOSP on crosshatch`.
- Remote gateway remains running. Temporary local smoke-test endpoints/processes were cleaned up. Startup trigger configuration was inspected without rebooting the PC. System VPN was not disabled; it was only needed for remote SSH management, not the tested ADB data path.
Desktop follow-up:
- Avalonia now defaults to `wss://ttstd.com/ads`, with explicit origin `175.178.213.60:443`. HTTPS catalog requests and the Rust child share the same prefix/origin configuration; neither disables TLS validation.
- Twelve .NET tests passed: URI prefix/port handling, invalid configuration, migration, role-token import, environment isolation and non-persistence, and rejection of an untrusted local TLS certificate even with an origin override.
- Official Avalonia headless tests loaded the real XAML and checked bindings/button state. Real live-device tests passed public catalog discovery, GUI command connect, ADB readiness, model/Android/API display, reconnect, disconnect and lease release.
- Official scrcpy 5.0.1 archive matched its published SHA-256. The desktop command started real public video streaming; scrcpy reported `Texture (D3D11VA): 944x1920`. Stop, reconnect and disconnect checks passed after that.
- Rendered normal and minimum-size layouts were inspected. No token was present in saved settings or UI logs. Windows self-contained publishing succeeded, excluding credentials.
- Native Windows UI automation could not initialize because its runtime reported a sandbox setup error. Tests were Avalonia headless plus real network/process/video operations; native mouse/keyboard, clipboard/file picker and tray behavior have not been automatically exercised in this run.
Port cleanup follow-up:
- Added the clear-port action to the connection card and local connection settings. Windows reads native IPv4/IPv6 TCP listener tables; non-Windows uses lsof when available.
- Cleanup rechecks port ownership and process creation time, terminates only the matching process (not its entire process tree), verifies the port can be bound, and removes the corresponding local ADB endpoint.
- Fifteen .NET tests passed, including actual disposable listener-process termination, unrelated-process survival, stale identity rejection, and protection for the current process / ADB main-service port.
- Avalonia headless test invoked the new command against a real child listener and verified both process exit and port release. Temporary listener children were cleaned up after testing.